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] Wed Dec 21 03:18:04 -0800 2005 ------- >wrt JCA, How can I do this? >I as a gnome-user don't like the idea of not supporting gnome. As I mentioned: with the package that I sent GNOME is partially supported i.e. menu entries are visible but icons may not be displayed. >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. In step 6 and 8 I do NOT modify desktop files themselves. I only modify symbolic links to them. In step 7) openoffice.org-2.0-printeradmin, openoffice.org-2.0 in usr/bin are indeed changed but these files are simple bash scripts and can be recreated using another simple bash script where a variable defining installation path can be declared. >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. Apparently KDE is doing it itself as new entries in KDE menu were visible right after package installation (no need to updated anything manually or to re-login into KDE) >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. for the steps 6-8 everything can be solved with one bash script where a variable defining installation path can be declared. So from one release to another, maintainer would have only to change one and only one variable. ;) > 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. Slackware is about simplicity. What makepkg tool is doing is automation of some manual steps i.e. - change ownership of files (if desired) - remove symlinks and create script doinst.sh so that symlinks can be recreated during installation - tar and gzip content of working directory. So makepkg is not necessary. --------------------------------------------------------------------- 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]
