Summary: | java-config forced on all pkgs inheriting java-pkg.eclass when USE=-java is set | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | solar (RETIRED) <solar> |
Component: | New packages | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | Florian.Steinel, greg, henrik, siryes |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
solar (RETIRED)
2006-06-25 13:20:41 UTC
That will not work either. On one hand, it will fix the specific problem for packages with optional Java support ie IUSE=java. On the other, it will introduce the java use flag on every single package that inherits it, including packages that are pure java. And then, it will only pull in java-config if you have USE=java. There may be cases where the user is installing java stuff, but does not have USE=java, and in these cases, they wouldn't get java-config pulled in. This problem was considered for the new Java system and eclasses, and is solved by the java-pkg-opt-2 eclass. Basically, this does something like: DEPEND="java? ( ${JAVA_CONFIG_DEP} )" RDEPEND="java? ( ${JAVA_CONFIG_DEP} )" This way, pure java packages inherit java-pkg-2, and get the dep as they expect. And packages with optional java support inherit java-pkg-opt-2, and only get the depends with USE=java. *** Bug 137923 has been marked as a duplicate of this bug. *** After thinking about it a little bit, I realized that JDKs and JREs already depend on java-config. And since we depend on JDKs for building, that should be enough to make java-config available. Fixed in CVS. Thanks for reporting. *** Bug 137993 has been marked as a duplicate of this bug. *** |