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