On 09/02/2015 06:18 PM, Ian Stakenvicius wrote: > > There's no "best" slot, slots aren't used the same as versions -- > they either match or differ. The slot that's preferred (in portage > at least, i expect other PMs too) is the SLOT of the most recent > version of the package that's emerge'able. >
Absolutely correct. I must have been confused, because some PMs actually do use the term "best slot". > In terms of libraries in general, although the SLOT=0 for full > package version / SLOT=somethingelse for binary-only stuff is a bit > of a convention, you need to check what slotting actually means for > every dependency your package depends on because each one will > differ. For instance, sci-libs/opencascade installs all versions in > their own specific slot, headers and all. The choice generally > comes down to what the maintainer of the library package decides to do > . > This is another case where I feel we need better metadata support (or at least some documentation policy/standard, so developers don't go into pitfalls). With the rise of SUBSLOTs this becomes even more a problem, because they also can mean a few different things.
