Latest eclipse-sdk-3.1.2-r2.ebuild contain dependancy to ant. I've just succesfully emerged this ebuild having only ant-core installed. To do this I removed ant dependancy and leaved only ant-core one in ebuild. It'll be good to fix this, because it could save traffic of downloading all full ant dependancy packages.
dev-java/ant is a 'meta-package'. This means it just pulls in dev-java/ant-core and dev-java/ant-tasks. You would have to unmerge dev-java/ant-tasks in order to verify that the dependency could be just dev-java/ant-core.
(In reply to comment #1) > dev-java/ant is a 'meta-package'. This means it just pulls in dev-java/ant-core > and dev-java/ant-tasks. You would have to unmerge dev-java/ant-tasks in order > to verify that the dependency could be just dev-java/ant-core. > I don't have ant-taks installed. I have only ant-core, and after fixing ebuild (removing dev-java/ant dependancy) eclipse emerged without any problems.
Since my issue is very similar I'm posting it here, instead of opening another bug: conan gfaccin # emerge eclipse-sdk -p These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] www-client/seamonkey-1.0.3 USE="crypt gnome ipv6 -debug -java -ldap -mozcalendar -mozdevelop -moznocompose -moznoirc -moznomail -moznoroaming -postgres -xinerama -xprint" (other packages) [ebuild N ] dev-util/eclipse-sdk-3.2 USE="gnome opengl -cairo -no-seamonkey" Maybe I'm not undestanding it; but why is eclipse-sdk requiring seamonkey if it's being built with a no-seamonkey flag? This dependency is prohibiting me from installing eclipse since seamonkey does not compile on amd64 (see bug #147252 ).
(In reply to comment #3) > Since my issue is very similar I'm posting it here, instead of opening another > bug: > > > conan gfaccin # emerge eclipse-sdk -p > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild N ] www-client/seamonkey-1.0.3 USE="crypt gnome ipv6 -debug -java > -ldap -mozcalendar -mozdevelop -moznocompose -moznoirc -moznomail -moznoroaming > -postgres -xinerama -xprint" > (other packages) > [ebuild N ] dev-util/eclipse-sdk-3.2 USE="gnome opengl -cairo > -no-seamonkey" > > > > Maybe I'm not undestanding it; but why is eclipse-sdk requiring seamonkey if > it's being built with a no-seamonkey flag? This dependency is prohibiting me > from installing eclipse since seamonkey does not compile on amd64 (see bug > #147252 ). > See how it says -no-seamonkey? That means it's _not_ being built with no-seamonkey, and therefore requires seamonkey. There is a bug open for changing no-seamonkey to seamonkey at bug 94756. Aside from that, this is an entirely differnet issue.
The current stable version of dev-util/eclipse-sdk uses the seamonkey use flag properly. This boils down to if eclipse users expect full ant to be available. I would say to require only optional tasks with no extra deps as eclipse binary release probably doest not bundle the deps any way so that should give us the same functionality as the upstream release.
Currently eclipse depends on ant-core and ant-nodeps. This needs to be rechecked against eclipse-sdk-3.3.1.1 to see what that version does.
As comment 5 says, we need to distinguish what parts of ant eclipse needs to compile itself, and what it bundles (and we replace with system installed jars) for users to use ant in eclipse. Perhaps the second should be triggered by an use flag?
It seems 3.3.1.1 only depends on ant-core and ant-nodeps for building, and also only those are provided to the user using ant within eclipse. The later part is questionable but for a possible different bug, this one is therefore closed.
