-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 08/12/13 03:21 PM, Tom Wijsman wrote: > On Sun, 8 Dec 2013 21:01:00 +0100 Ulrich Mueller <u...@gentoo.org> > wrote: > >>>>>>> On Sun, 8 Dec 2013, Rich Freeman wrote: >> >>> Sure it does - it defaults to :* when :* was never specified. >>> I don't see how defaulting to :0= is a "policy" any more than >>> :* is. >> >> Defaulting to :* is just the long term behaviour from EAPIs 0 to >> 4 when no slot operator was specified. > > Which section in the PMS is this specified? > >> This is consistent with what we haved for versioned >> dependencies. When you don't specify a version, then all versions >> are good. > > Good idea. > >> Similarly, when you don't specify a slot, then all slots are >> good. > > Not so good idea; because if all slot would be good by default, > then why have slots in the first place? Are we using SLOT right at > all? >
SLOT allows multiple versions of a package to be installed concurrently. In the case of libraries or dependencies, this supports the specific case where certain ebuilds only support a particular SLOT. However, that doesn't mean that all packages need to be tied to one slot or another. It should be noted here that this discussion is revolving entirely around multi-SLOT libraries. Firstly, there are packages like dev-db/postgresql that use SLOTs not just for library provision. Secondly, SLOT= on the libraries being discussed may not actually be the correct method to deal with this at all, and rather, these libs should be using a subslot and the rdeps be using an upper-bound version on dependency atoms to limit which dependency it can be used with--it all depends on whether the library maintainer intends to support both major versions in the long term or not. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlKngmsACgkQ2ugaI38ACPCfxwD/YifeWm+rrAN1om9HP41ATO6Z pqKChxQaayjzfWtKyeMA/2K9AJFvhowBSKHBatAilfWGuI2L25dMHFidOxzLpZX3 =KW2i -----END PGP SIGNATURE-----
