I have on my system Ant 1.5.4 installed because I installed jboss. Now Ant 1.6.2 has just become stable so portage wants to upgrade it. However it wants also to install *21* new packages because Ant now *requires* Ant-Optional which depends on quite a few packages. The total of new packages to install in my configuration is *40969kB*. So: - if ant-optional is really required, it should be renamed. - it should also use some USE flags or something, the number and size of all the dependencies are just ridiculous. Why would I need bcel or jython or jsch or rhino just to run just to have a "make" equivalent for java.
After reading bug 41889, I know what's going on here, but do not agree with the resolution of it. Why not just say in pkg_postinst() of ant "you might want to take a look at ant-optional for additional ant tools" and drop the requirement for it as it is now. Solution without that of course is a: emerge --inject ant-optional-1.6.2-r2
*** Bug 62057 has been marked as a duplicate of this bug. ***
I also disagree with the resolution of bug 41889. Java team, please take steps to resolve this issue in some other way.
ant, needs to depend on ant-optional, because if we have ebuilds depending on ant-optional there is no way to make sure it depends on the same version as the version of ant installed? If we make an optional useflag for ant, we would need useflag based depends. We could add a set off noX use flags in ant-optional. But if forsee bugs reports because someone noX'd things a package needs, again there are no useflag based deps. ant-tasks would probably be a better name for ant-optional
ant-optionals simply should depend on the exact version of ant. For Example ant-optionals-1.6 should depend on ant-1.6.*. Well, if an older version of ant is installed, than ant will be upgradet. A problem is, when an upgrade to ant is available. Than ant will get upgraded, but the portage doesn't complain about that, since it doesn't keep the package-dependencies consistent. portage should know how to reolve that, shouldn't it? Well, your way of doing it, doesn't work either. If an upgrade to ant-optionals is available, portage will upgrade them, and the dependency by ant (which is ant-optionals-1.6* for example) would be broken i guess.
the way i was refering to basicly how it is now, and it does work when there is an update for ant-optional there is always one for ant there basicly the same. And ant blocks <ant-optional-${PV} because if you have diffrend versions of ant and ant-optional installed ant no longer works, so you have to unmerge ant-optional, upgrade ant, then upgrade ant-optional. Because when ant-optional's deps also have updates, and you upgrade ant, it'll try to update those deps b4 ant-optional gets upgraded, and ant won't work for them There is no clean simple solution here...
in ~x86 ant-optional has been renamed to ant-tasks with noX useflag to disable things
just commited a few fixes(ant-tasks-1.6.2-r3)
Hi guys I haven't checked looked at the ebuilds at all, but I almost fell out of my chair, when I saw the output after emerge -upD world. First question I have is, why does ant want to install: dev-java/blackdown-jdk-1.4.1 if I already have: * dev-java/sun-jdk Latest version available: 1.4.2.05 Latest version installed: 1.4.2.05 installed I really don't understand, why all of a sudden there are so many packages needed. Note I currently have ant 1.6.0 installed.
ant-optional has been renamed to ant-tasks with noX use flags
