-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 02/09/15 11:15 AM, hasufell wrote: > On 09/02/2015 05:06 PM, George Shapovalov wrote: >> On Wednesday 02 September 2015 16:29:52 hasufell wrote: >>>> - >=sys-libs/ncurses-5.7" + >=sys-libs/ncurses-5.7:*" >>> This doesn't look correct to me, unless dev-lang/gnat-gcc >>> doesn't need ncurses headers(?). Only sys-libs/ncurses:0 >>> provides headers (the other slots are for binary >>> compatibility), so we probably want to depend on SLOT :0. In >>> addition, if we fix the SLOT to :0, we should do a revbump to >>> ensure that user VDB is updated correctly. >> Ah, Ok, thanks for heads up on ncurses (OTOH this is a bit >> strange - different slots provide not just incompatible but >> drastically different contents. Shouldn't there be a separate >> -headers package then? The deps would be kind of more evident >> in such case..). This was a part of general change to fix >> repoman complaints. I'll fix the ncurses part and do a revbump >> to update VDB then.. >> >> >> > > Well, it isn't particularly nice, because we don't have proper > SLOT descriptions (although SLOT can contain any of the > characters [A-Za-z0-9+_.-], but then I am not sure how the PM > decides about the "best" SLOT... I couldn't find a useful answer > in PMS). > > However, this slotting method is already used in libraries like > media-libs/libpng or dev-libs/openssl, so it seems it silently > became a standard. >
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. 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 . -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlXnIUEACgkQAJxUfCtlWe2TMQEAqwtrleALZNxUeBJzxtilTY19 6+ndXbA0GeY70HpWvdQA/jEB87y+zQoP7J/HMXOZRMHa5bRfwAyZLO8t5VloScyd =U6d6 -----END PGP SIGNATURE-----
