Right now, the symlinks to run OpenOffice.org components are a complete mess:
$ pkg_info -L openoffice.org-2.0.2.rc1 | grep /usr/local/bin
This contrasts with the default Gentoo installation:
$ equery files openoffice | grep '/usr/bin'
If possible, could the port be modified to use symlinks similar to the ones Gentoo uses? Typing "oowriter2" is a lot easier than "openoffice.org-2.0.2.rc1-swriter", and much more scripting-friendly.
I'm not sure whether editing the post-install clause in the port Makefile is sufficient, or if the build process needs to be patched so that the /usr/local/bin/openoffice.org-2.0.2.rc1 binary knows how to switch its behavior based on the new names it would called as. My initial experiments with making new symlinks called "oowriter2", "oowriter", and "swriter" and hoping that OpenOffice.org would DWIM did not look promising; they all resulted in the "generic" application being loaded. I'm too intimidated by this port to do serious investigation and so demurely leave judgment to the experts.
How-To-Repeat: Install the editors/openoffice.org-2.0 port and hear shell tab-completion play the Ukrainian Bell Carol as you try to run one of the components.
Over to maintainer(s).
Does this problem still recur with the latest openoffice?
Submitter no longer uses openoffice.