| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 08/12/13 03:21 PM, Tom Wijsman wrote: |
| 5 |
> On Sun, 8 Dec 2013 21:01:00 +0100 Ulrich Mueller <ulm@g.o> |
| 6 |
> wrote: |
| 7 |
> |
| 8 |
>>>>>>> On Sun, 8 Dec 2013, Rich Freeman wrote: |
| 9 |
>> |
| 10 |
>>> Sure it does - it defaults to :* when :* was never specified. |
| 11 |
>>> I don't see how defaulting to :0= is a "policy" any more than |
| 12 |
>>> :* is. |
| 13 |
>> |
| 14 |
>> Defaulting to :* is just the long term behaviour from EAPIs 0 to |
| 15 |
>> 4 when no slot operator was specified. |
| 16 |
> |
| 17 |
> Which section in the PMS is this specified? |
| 18 |
> |
| 19 |
>> This is consistent with what we haved for versioned |
| 20 |
>> dependencies. When you don't specify a version, then all versions |
| 21 |
>> are good. |
| 22 |
> |
| 23 |
> Good idea. |
| 24 |
> |
| 25 |
>> Similarly, when you don't specify a slot, then all slots are |
| 26 |
>> good. |
| 27 |
> |
| 28 |
> Not so good idea; because if all slot would be good by default, |
| 29 |
> then why have slots in the first place? Are we using SLOT right at |
| 30 |
> all? |
| 31 |
> |
| 32 |
|
| 33 |
SLOT allows multiple versions of a package to be installed |
| 34 |
concurrently. In the case of libraries or dependencies, this supports |
| 35 |
the specific case where certain ebuilds only support a particular |
| 36 |
SLOT. However, that doesn't mean that all packages need to be tied to |
| 37 |
one slot or another. |
| 38 |
|
| 39 |
It should be noted here that this discussion is revolving entirely |
| 40 |
around multi-SLOT libraries. Firstly, there are packages like |
| 41 |
dev-db/postgresql that use SLOTs not just for library provision. |
| 42 |
Secondly, SLOT= on the libraries being discussed may not actually be |
| 43 |
the correct method to deal with this at all, and rather, these libs |
| 44 |
should be using a subslot and the rdeps be using an upper-bound |
| 45 |
version on dependency atoms to limit which dependency it can be used |
| 46 |
with--it all depends on whether the library maintainer intends to |
| 47 |
support both major versions in the long term or not. |
| 48 |
|
| 49 |
|
| 50 |
-----BEGIN PGP SIGNATURE----- |
| 51 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 52 |
|
| 53 |
iF4EAREIAAYFAlKngmsACgkQ2ugaI38ACPCfxwD/YifeWm+rrAN1om9HP41ATO6Z |
| 54 |
pqKChxQaayjzfWtKyeMA/2K9AJFvhowBSKHBatAilfWGuI2L25dMHFidOxzLpZX3 |
| 55 |
=KW2i |
| 56 |
-----END PGP SIGNATURE----- |
Archives