After I emerged ant and was emerging portagemaster I got this error "Could not
find package ant". Typing ant would give the same error. After digging around
found that the ant script uses java-config to query the class of the package
ant and sets it. However, ant is an empty package. It does not have files
associated with it. The ant files are actually under the package ant-core. Not
sure why this is but. When I changed the java-config query command to look up
the classpath of ant-core, it started working.
#vi `which ant`
change:
# add in the dependency .jar files
LOCALCLASSPATH="${LOCALCLASSPATH}:`java-config --classpath=ant`"
to read:
# add in the dependency .jar files
LOCALCLASSPATH="${LOCALCLASSPATH}:`java-config --classpath=ant-core`"
Reproducible: Always
Steps to Reproduce:
1.Emerge Ant
2.Emerge any other ebuild which uses ant(ie. portagemaster)
3.
Actual Results:
You get "Could not find package ant" and no package which uses ant will work,
and give error about not finding Main in the class.
Expected Results:
It should work? Ant ebuild should set the correct classpath.
This is a minor bug, as in the bug details I show how I fixed it. I just
would like to enter a bug and have it fixed for future ebuilds.
