1 |
On Wed, 05 Dec 2012 04:42:23 -0500 |
2 |
Alexandre Rostovtsev <tetromino@g.o> wrote: |
3 |
> Suppose I am upgrading an existing ebuild for dev-libs/libfoo-2.5 to |
4 |
> EAPI5 and adding a subslot, e.g. SLOT="2/5". Should I then add |
5 |
> "slotmove =dev-libs/libfoo-2.5 2 2/5" in profiles/updates? Or should |
6 |
> it be "slotmove =dev-libs/libfoo-2.5 2/2 2/5" (since the PMS states |
7 |
> that "When the sub-slot part is omitted from the SLOT definition, the |
8 |
> package is considered to have an implicit sub-slot which is equal to |
9 |
> the regular slot")? Will this update even do what one would |
10 |
> intuitively expect it to do? Might it break older versions of portage |
11 |
> on emerge --sync? |
12 |
|
13 |
You can't put subslots in updates, since it's not EAPI controlled. |
14 |
|
15 |
-- |
16 |
Ciaran McCreesh |