Add mechanism for enforcing ordering of wheelhouse install about layer-basic

[marcoceppi]

This seems like a sane approach

[mbruzek]

@johnsca So in this case the wheelhouse.txt files do not overwrite other layers? These text files are combined arbitrarily where other files with the same name are overwritten.

[johnsca]

@mbruzek wheelhouse.txt files do not override that of other layers under the assumption that a given layer knows what its dependencies are and those shouldn't be mucked about by other layers. You can think of it as they are merged by appending according to the usual rules but then the resultant combined wheelhouse.txt is not kept around.

I can see where this may cause problems down the road if two layers try to pull in different versions of the same lib. I'm not sure how best to handle this.

[marcoceppi]

@johnsca it seems we'd need to built a merge tactic for wheelhouse.txt
where we either always use the lowest (or highest) version, add a way to
delete keys from wheelhouse.txt, or error the build if there are two
versions of an entry that conflict in wheelhouse.txt

On Fri, Apr 15, 2016 at 5:01 PM Cory Johns [email protected] wrote:

@mbruzek https://github.com/mbruzek wheelhouse.txt files do not
override that of other layers under the assumption that a given layer knows
what its dependencies are and those shouldn't be mucked about by other
layers. You can think of it as they are merged by appending according to
the usual rules but then the resultant combined wheelhouse.txt is not
kept around.

I can see where this may cause problems down the road if two layers try to
pull in different versions of the same lib. I'm not sure how best to handle
this.

—
You are receiving this because you commented.

Reply to this email directly or view it on GitHub
#55 (comment)