Summary: | [metabug] Making packages depend on dev-java/ant-core instead of dev-java/ant when possible | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Petteri Räty (RETIRED) <betelgeuse> |
Component: | [OLD] Unspecified | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | tristan |
Priority: | High | Keywords: | Tracker |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.gentoo.org/proj/en/java/java-devel.xml | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | patch for java-devel.xml |
Description
Petteri Räty (RETIRED)
2005-10-24 08:53:09 UTC
Created attachment 71337 [details, diff] patch for java-devel.xml Here is a proposed patch against http://gentooexperimental.org/svn/java/axxo-overlay/README/docs/java-devel.xml to improve the documentation. I fixed dev-java/xmldb and dev-java/aspectj is bogus. It is dev-java/adaptx that failed. commons-httpclient-3.0_rc4 fixed Last night nichoj fixed dev-java/saxpath and earlier dev-java/commons-dbcp We have to be careful about ant dependencies... I just fixed xdoclet, where it only had ant-core, but needed ant-tasks for normal compilation. (In reply to comment #5) > We have to be careful about ant dependencies... I just fixed xdoclet, where it > only had ant-core, but needed ant-tasks for normal compilation. That is why I always turn off LOCALCLASSPATH in /usr/bin/ant and start with no packages installed before changing to just ant-core. Fixed dev-java/picocontainer Is there an easy way to check that a package only needs dev-java/ant-core without removing everything that comes with dev-java/ant before testing? (In reply to comment #8) > Is there an easy way to check that a package only needs dev-java/ant-core > without removing everything that comes with dev-java/ant before testing? > Add JAVA_PKG_STRICT=1 to make.conf Well JAVA_PKG_STRICT=1 makes sure there are not unsatisfied deps. One way to do it is to remove the ant-tasks package and it to package.provided. This should make packages that need full ant fail. (In reply to comment #8) > Is there an easy way to check that a package only needs dev-java/ant-core > without removing everything that comes with dev-java/ant before testing? > It will be possible with the split-ant packaging I'm working on. JAVA_PKG_STRICT=1 will disable optional tasks if there's only ant-core in DEPEND. And you will be able to override it with envvar to test without modifying the ebuild. dev-java/lucene modified This bug was solved ages ago, any new cases of this would be exceptional and need not be meta-tracked. |