| 1 |
Suppose I am upgrading an existing ebuild for dev-libs/libfoo-2.5 to |
| 2 |
EAPI5 and adding a subslot, e.g. SLOT="2/5". Should I then add |
| 3 |
"slotmove =dev-libs/libfoo-2.5 2 2/5" in profiles/updates? Or should it |
| 4 |
be "slotmove =dev-libs/libfoo-2.5 2/2 2/5" (since the PMS states that |
| 5 |
"When the sub-slot part is omitted from the SLOT definition, the package |
| 6 |
is considered to have an implicit sub-slot which is equal to the regular |
| 7 |
slot")? Will this update even do what one would intuitively expect it to |
| 8 |
do? Might it break older versions of portage on emerge --sync? |
| 9 |
|
| 10 |
Is there any difference between RDEPEND="dev-libs/libfoo:2" and |
| 11 |
RDEPEND="dev-libs/libfoo:2=" in an EAPI5 ebuild? Will both variants |
| 12 |
force a rebuild when the subslot of libfoo:2 changes? |
| 13 |
|
| 14 |
Can I use EAPI5 in a stable ebuild, as long as it's only marked stable |
| 15 |
on arches that have >=portage-2.1.11.31 stabilized? Or is EAPI5 still |
| 16 |
~arch-only until the council declares otherwise? |
Archives