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 is omitted from the SLOT definition, the package is considered to have an implicit sub-slot which is equal to the regular slot")? Will this update even do what one would intuitively expect it to do? Might it break older versions of portage on emerge --sync?
Is there any difference between RDEPEND="dev-libs/libfoo:2" and RDEPEND="dev-libs/libfoo:2=" in an EAPI5 ebuild? Will both variants force a rebuild when the subslot of libfoo:2 changes? Can I use EAPI5 in a stable ebuild, as long as it's only marked stable on arches that have >=portage-2.1.11.31 stabilized? Or is EAPI5 still ~arch-only until the council declares otherwise?
