To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=59183





------- Additional comments from [EMAIL PROTECTED] Tue Dec 20 13:43:55 -0800 
2005 -------
wrt JCA, yes - one can argue about the level of "coding" involved.. Sure the
attached one doesn't include anything worth a JCA or similar, but embedding this
 into the build-system (automating these steps) may result in a makefile with
considerably more "coding".. And preferably this should not be a onetimer, but
as well keeping it up-to-date as development of OOo itself continues.

I as a gnome-user don't like the idea of not supporting gnome.

and wrt steps 6-8) modifying the desktop files, etc. to point "to the right
directory" is arguable as well, the link in /etc/ is meant to keep the packages
relocatable. You have the link in /etc/ point to the right directory.

regarding point 2) it is not enough to only place the files in the directories,
you have to update the cache for the mime and menu files.

Anyway regarding the link-locations I'd prefer that you keep the symlink in
/etc, just like it is done for the other distros. If it is not possible to query
for an install-location for slackware packages, then it at least eases the
maintainer's task when he decides to not place OOo into /opt/openoffice.org2.0 
- he only has to modify one single link instead of every single link.

Anyway- I accept this issue and I'm willing to handle the technical stuff
(integration into build-system, creation of cws, etc.) - But I'm not sure about
relying on the makepkg tool. I don't want to add a dependency to OOo, so if that
stuff can be created without that tool, this should be the way to go.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to