When I noticed that installing openoffice removed dmake I assumed that it was for a command collision with dmake the openoffice buildsystem, but with the current Portage (2.1.6), the removal of dmake happens _after_ OOo has been built correctly: <<< dir /usr/lib/openoffice/basis3.0/program/defaults/pref <<< dir /usr/lib/openoffice/basis3.0/program/defaults/autoconfig <<< dir /usr/lib/openoffice/basis3.0/program/defaults <<< dir /usr/lib/openoffice/basis3.0/program/components <<< dir /usr/lib/openoffice/basis3.0/program/classes <<< dir /usr/lib/openoffice/basis3.0/help/en/swriter.idxl <<< dir /usr/lib/openoffice/basis3.0/help/en/smath.idxl <<< dir /usr/lib/openoffice/basis3.0/help/en/simpress.idxl <<< dir /usr/lib/openoffice/basis3.0/help/en/sdraw.idxl <<< dir /usr/lib/openoffice/basis3.0/help/en/sdatabase.idxl <<< dir /usr/lib/openoffice/basis3.0/help/en/schart.idxl <<< dir /usr/lib/openoffice/basis3.0/help/en/scalc.idxl <<< dir /usr/lib/openoffice/basis3.0/help/en/sbasic.idxl --- !empty dir /etc/revdep-rebuild >>> Uninstalling dev-util/dmake-4.1-r1 dev-util/dmake selected: 4.1-r1 protected: none omitted: none >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. >>> Unmerging dev-util/dmake-4.1-r1... No package files given... Grabbing a set. <<< obj /usr/share/dmake/startup/unix/xenix/macros.mk <<< obj /usr/share/dmake/startup/unix/sysvr4/macros.mk <<< obj /usr/share/dmake/startup/unix/sysvr3/macros.mk <<< obj /usr/share/dmake/startup/unix/sysvr3/gnu/macros.mk <<< obj /usr/share/dmake/startup/unix/sysvr1/macros.mk <<< obj /usr/share/dmake/startup/unix/solaris/macros.mk <<< obj /usr/share/dmake/startup/unix/recipes.mk <<< obj /usr/share/dmake/startup/unix/macros.mk <<< obj /usr/share/dmake/startup/unix/linux/macros.mk <<< obj /usr/share/dmake/startup/unix/linux/gnu/macros.mk <<< obj /usr/share/dmake/startup/unix/coherent/recipes.mk <<< obj /usr/share/dmake/startup/unix/coherent/macros.mk <<< obj /usr/share/dmake/startup/unix/bsd43/recipes.mk <<< obj /usr/share/dmake/startup/unix/bsd43/macros.mk <<< obj /usr/share/dmake/startup/unix/386ix/macros.mk <<< obj /usr/share/dmake/startup/startup.mk <<< obj /usr/share/dmake/startup/config.mk <<< obj /usr/bin/dmake <<< dir /usr/share/dmake/startup/unix/xenix <<< dir /usr/share/dmake/startup/unix/sysvr4 <<< dir /usr/share/dmake/startup/unix/sysvr3/gnu <<< dir /usr/share/dmake/startup/unix/sysvr3 <<< dir /usr/share/dmake/startup/unix/sysvr1 <<< dir /usr/share/dmake/startup/unix/solaris <<< dir /usr/share/dmake/startup/unix/linux/gnu <<< dir /usr/share/dmake/startup/unix/linux <<< dir /usr/share/dmake/startup/unix/coherent <<< dir /usr/share/dmake/startup/unix/bsd43 <<< dir /usr/share/dmake/startup/unix/386ix <<< dir /usr/share/dmake/startup/unix <<< dir /usr/share/dmake/startup <<< dir /usr/share/dmake * Messages for package app-office/openoffice-3.0.0: Since there is no collision between dmake and openoffice at runtime, what is the blocker there for?
(In reply to comment #0) > When I noticed that installing openoffice removed dmake I assumed that it was > for a command collision with dmake the openoffice buildsystem, but with the > current Portage (2.1.6), the removal of dmake happens _after_ OOo has been > built correctly: > > Since there is no collision between dmake and openoffice at runtime, what is > the blocker there for? Historically a system installed dmake did result in OOo build breakage (which uses its own dmake), so we put a blocker on this. But I didn't check if that's still true, so if you say that OOo now merges just fine with a installed dmake, we should remove that blocker.
I've removed the blocker now, thanks for pointing this out. Closing.
