package app-arch/fastjar-0.95 NOT merged Searching all installed packages for file collisions... Press Ctrl-C to Stop * dev-java/kaffe-1.1.7-r5: '/usr/share/info/fastjar.info.bz2' '/usr/share/man/man1/fastjar.1.bz2' Given that kaffe depends on fastjar, fastjar package's man and info should stay and kaffe's copy should go... possibly replace even kaffe's own fastjar binary with symlink to system fastjar and make it a RDEPEND?
-r6 now uses system copies of zlib and fastjar. There is a bug in kaffe with --disable-fastjar that it does not make the jar wrapper point to system fastjar. I will need to see with dalibor to report this. For now I just used dosym.
Is there any reason why we don't make app-arch/fastjar-0.95 block <=dev-java/kaffe-1.1.7-r5? That way the kaffe-1.1.7-r6 upgrade will happen before the fastjar-0.95 upgrade when necessary, preventing the user from experiencing a file collision. [ebuild U ] dev-java/kaffe-1.1.7-r6 [1.1.7-r5] USE="alsa esd gmp gtk nls" 0 kB [ebuild U ] app-arch/fastjar-0.95 [0.94] 0 kB [1] I don't see the blocker causing any problems, but maybe I'm missing something.
Yeah I also had the wrong order and wondered bout this. If portage is smart enough, why not.
Ok, so app-arch/fastjar-0.95 blocks <=dev-java/kaffe-1.1.7-r5 in RDEPEND, seems to help, kaffe is now upgraded first. Also, all kaffe versions <=1.1.7-r6 block on >=app-arch/fastjar-0.95 in RDEPEND, to be sure people don't install new fastjar and then old kaffe. Now we just have to remember we need to stabilize kaffe -r6 before fastjar 0.95...
