| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 05/12/12 04:42 AM, Alexandre Rostovtsev wrote: |
| 5 |
> Suppose I am upgrading an existing ebuild for dev-libs/libfoo-2.5 |
| 6 |
> to EAPI5 and adding a subslot, e.g. SLOT="2/5". Should I then add |
| 7 |
> "slotmove =dev-libs/libfoo-2.5 2 2/5" in profiles/updates? Or |
| 8 |
> should it be "slotmove =dev-libs/libfoo-2.5 2/2 2/5" (since the PMS |
| 9 |
> states that "When the sub-slot part is omitted from the SLOT |
| 10 |
> definition, the package is considered to have an implicit sub-slot |
| 11 |
> which is equal to the regular slot")? Will this update even do what |
| 12 |
> one would intuitively expect it to do? Might it break older |
| 13 |
> versions of portage on emerge --sync? |
| 14 |
> |
| 15 |
> Is there any difference between RDEPEND="dev-libs/libfoo:2" and |
| 16 |
> RDEPEND="dev-libs/libfoo:2=" in an EAPI5 ebuild? Will both |
| 17 |
> variants force a rebuild when the subslot of libfoo:2 changes? |
| 18 |
> |
| 19 |
> Can I use EAPI5 in a stable ebuild, as long as it's only marked |
| 20 |
> stable on arches that have >=portage-2.1.11.31 stabilized? Or is |
| 21 |
> EAPI5 still ~arch-only until the council declares otherwise? |
| 22 |
> |
| 23 |
> |
| 24 |
|
| 25 |
1. slotmove doesn't work for sub-slots, so no. |
| 26 |
|
| 27 |
1a. the implicit subslot text essentially means that if you only set |
| 28 |
"SLOT=2", then it rolls itself out to SLOT=2/2 in the background |
| 29 |
(vdb). This doesn't affect how you manage the package yourself, |
| 30 |
afaik. Note also that I haven't actually examined this so i can't |
| 31 |
confirm that SLOT=2/2 would be the actual value written in the vdb. |
| 32 |
|
| 33 |
2. dev-libs/libfoo:2 is the same as dev-libs/libfoo:2* , which |
| 34 |
differs from dev-libs/libfoo:2= . Essentially you would use :2= when |
| 35 |
you want this package to remain solely dependent on slot 2, but |
| 36 |
rebuild when sub-slot changes occur in libfoo within slot 2. Without |
| 37 |
the = slot-operator, rebuilds will not be triggered. |
| 38 |
|
| 39 |
3. EAPI5 can be used in stable ebuilds as long as >=portage-2.1.11.20 |
| 40 |
is stable on all of the stable keywords in that ebuild. Council was |
| 41 |
clear that as soon as an EAPI5-capable portage was stable it could be |
| 42 |
used in stable ebuilds. |
| 43 |
|
| 44 |
That said, it is recommended that you revbump for EAPI5; it is not |
| 45 |
strictly necessary, but without the revbump users with that version |
| 46 |
already installed will not receive the benefits of the |
| 47 |
sub-slot/slot-operator, since the sub-slot has to be written to the |
| 48 |
vdb for both the package and all rdeps with slot-operator atoms. |
| 49 |
|
| 50 |
-----BEGIN PGP SIGNATURE----- |
| 51 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 52 |
|
| 53 |
iF4EAREIAAYFAlC/TbgACgkQ2ugaI38ACPC23wD/T5fEzWbJJs/VptIHE37l6F1M |
| 54 |
6ntTByLRkHcVxiy3CJcBALvVvaC7Y0Y5XTzCmdKXvGiuqRKhKMu/+8Iq8SuKZ82T |
| 55 |
=a+HV |
| 56 |
-----END PGP SIGNATURE----- |
Archives