-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/12/12 10:06 AM, Ciaran McCreesh wrote:
> On Wed, 05 Dec 2012 08:35:52 -0500 Ian Stakenvicius
> wrote:
>> That said, it is recommended that you revbump for EAPI5; it is
>> not strictly necessary, but without the revbump users with that
>> versi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 05 Dec 2012 08:35:52 -0500
Ian Stakenvicius wrote:
> That said, it is recommended that you revbump for EAPI5; it is not
> strictly necessary, but without the revbump users with that version
> already installed will not receive the benefits of
On Wed, 05 Dec 2012 04:42:23 -0500
Alexandre Rostovtsev wrote:
> Suppose I am upgrading an existing ebuild for dev-libs/libfoo-2.5 to
> EAPI5 and adding a subslot, e.g. SLOT="2/5". Should I then add
> "slotmove =dev-libs/libfoo-2.5 2 2/5" in profiles/updates? Or should
> it be "slotmove =dev-libs/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/12/12 04:42 AM, Alexandre Rostovtsev wrote:
> Suppose I am upgrading an existing ebuild for dev-libs/libfoo-2.5
> to EAPI5 and adding a subslot, e.g. SLOT="2/5". Should I then add
> "slotmove =dev-libs/libfoo-2.5 2 2/5" in profiles/updates? Or
Suppose I am upgrading an existing ebuild for dev-libs/libfoo-2.5 to
EAPI5 and adding a subslot, e.g. SLOT="2/5". Should I then add
"slotmove =dev-libs/libfoo-2.5 2 2/5" in profiles/updates? Or should it
be "slotmove =dev-libs/libfoo-2.5 2/2 2/5" (since the PMS states that
"When the sub-slot part i
