Dear all,
Is it normal that emerge, during its dependency resolution, only considers the
latest version of a package?
If yes, is there a way to tell emerge to consider all unmasked versions?
I first noticed this behavior on a old version of the package tree, where
- sys-auth/polkit-113-r4 had REQUIRED_USE="?? ( elogind systemd )"
- sys-auth/polkit-115-r3 had REQUIRED_USE="^^ ( consolekit elogind systemd )"
And emerge failed right away saying that sys-auth/polkit-115-r3 could be
installed (because its use flags wasn't configured).
I then tested with some testing ebuild, and the current version of portage has
the same behavior.
Best,
Michael
PS: testing
========================================= file pdepa-1.0.ebuild
EAPI=6
DESCRIPTION="low installable version"
HOMEPAGE=""
KEYWORDS="amd64"
SLOT="0"
IUSE="feature"
DEPEND=""
REQUIRED_USE=""
========================================= file pdepa-2.0.ebuild
EAPI=6
DESCRIPTION="high uninstallable version"
HOMEPAGE=""
KEYWORDS="amd64"
SLOT="0"
IUSE="feature"
DEPEND="!virtual/libc"
#REQUIRED_USE="^^ ( feature )"
========================================= test
osboxes /opt/pdepa # emerge -pv --autounmask y --autounmask-backtrack y
--backtrack 30 net-misc/pdepa
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] net-misc/pdepa-2.0::pdepa USE="-feature" 0 KiB
[blocks B ] virtual/libc ("virtual/libc" is blocking net-misc/pdepa-2.0)
