I've installed fop-bin and it would be redundant to install fop from source because of batiks dependencies. Here's a diff to fix the depency issue i had --- /usr/portage/dev-java/batik/batik-1.5.1-r1.ebuild 2004-09-21 13:59:06.352009477 +0200 +++ /usr/portage/dev-java/batik/batik-1.5.1-r1_new.ebuild 2004-09-21 13:58:56.258144719 +0200 @@ -10,7 +10,10 @@ IUSE="doc" DEPEND=">=virtual/jdk-1.3 dev-java/rhino + || ( + dev-java/fop-bin dev-java/fop + ) >=dev-java/xerces-2.6.2-r1 dev-java/ant" RDEPEND=">=virtual/jdk-1.3" Reproducible: Always Steps to Reproduce: 1. install dev-java/fop-bin 2. emerging batik would emerge dev-java/fop which is actually not needed Actual Results: emerging batik worked for me after i changed the DEPEND variable. I'm not sure though how to test the fop dependent features of batik.
i was actualy planning to remove fop-bin is there a reason to keep it around?
oh, i see, well i'm running an old p2-400 as testserver, there compiling fop and its dependencies will take forever ;-) My reason to use -bin wherever i can is to avoid long compile times. But I can live without it too, I'd just build bin-packages on my fast client-machine and emerge them on the slow one. It's actually just a matter convenience. If you were planning to remove fop-bin go ahead, it wouldn't affect me too much. Also I don't know any other good reasons why to keep fop-bin. Therefore i will unmerge fop-bin and follow your new path, I think this bug can be closed because of being unnecessary ;)
dev-java/fop-bin removed in favor of dev-java/fop
