The case which triggered my attention was actually
app-office/libreoffice with USE="java". pkg_setup (through
java-utils-2.eclass java-pkg_switch-vm [1]) expects to find a
functional JDK environment, even though jdom-jaxen is not required as
RDEPEND by anything inside java eclasses and libreoffice ebuild,
because in fact, it's only declared as PDEPEND (in order to have the
circularity sorted out).
Given this real-world example, the ASAP feature makes possible to have
jdom-jaxen pulled in, in time, even if it's not something that is
required to PMS-compliant PMs.
So? A few options:
1. implement the ASAP feature in Entropy and live with broken dependencies
2. live with broken dependencies
3. Fix the broken dependencies
4. Fix the broken dependencies and have PMS defining rules for
scheduling PDEPENDs.
[1] depend-java-query --get-vm "${JAVA_PKG_NV_DEPEND:-${DEPEND}}"
expects to find a sane JDK environment.
--
Fabio Erculiani
http://lxnay.com
