second 1.0.1rc3 build broken
Hello, Has anyone actually tried openoffice.org on debian ppc since the last rebuild of July 16th? I have the original rc3 build from July 14th installed and it works fine. However when I do a apt-get I now drag down... File: openoffice.org_1.0.0-pre1.0.1rc3_all.deb 11123 KB 07/16/02 10:42:00 ...which doesn't match the openoffice.org-bin_1.0.0-pre1.0.1rc3_powerpc.deb in timestamp. This combo crashes after the openoffice splash screen appears. Why are we mixing parts of the build here? Shouldn't we have a openoffice.org-bin_1.0.0-pre1.0.1rc3_powerpc.deb from 07/16/02 there as well? Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Desktop integration for distributions [was debian-openoffice Announcing OpenOffice.org 1.0.1]
Hi Kevin, this is the view of a system administrator with some knowledge of different systems. Kevin B. Hendricks schrieb am Mittwoch, 17. Juli 2002 um 11:28:16 -0400: > Let's think about the very basics for a second (go back to first > principles) and see if there is some common ground we can use: > > 1. Where exactly under Linux should OpenOffice.org be installed? Are there > official guidelines? Is this /opt or /usr/bin or what? Does this differ > from distribution to distribution? > What about other Unix (Solaris, FreeBSD, MacOSX, etc? For most Unixes the common approach is to 'divide' software in three sections: 1. system software (OS itself, and all related software, mostly software from OS-Vendor) which is installed in [/usr]/[s]bin. 2. Add-on Software, replacements, software compiled by the local admin is expected to be in /usr/local 3. Large Packages from other vendors, is expected to be in /opt i.e. kde/gnome, HP OpenView, Oracle, Tivoli Storage Manager, Lotus Domino ... to name some of these beasts. Depending on the system the interpretation what software fits in which category differs. I personally like the Debian-Way to say 'every package we distribute is OS-Vendor-Software and _must_ go into section one. But there are lots of other opinions :-))) > 2. More specifically, where should all of the pieces of OpenOffice.org be > installed? Are there specific directories ... /usr/share/ and /etc/ ... > that we could all agree on and what goes there. IMHO there is no best solution. A better approach is to provide the ability to enter specific paths at configure-time like many other programs so. Have a default which installs ooo into /opt/OpenOffice.org and leave the rest to the people. > To help guide this discussion, could you tell me where you put the various > pieces of OOo in your latest Debian versions (including workstation > pieces)? Perhaps someone from Mandrake could add their info as well. I > heard that OOo was part of the alpha RedHat releases as well. Does anyone > know where they are placing the pieces. > > 3. What additional pieces would augment or help OOo under Linux (and other > Unixes)? > > - fonts - ghostscript urw fonts > - any ttf free fonts around? > - templates, HowTo's etc > > How / where would these be installed? the same way, install it into /opt, but provide the option to change this. > 4. How does Debian currently handle localizations for languages? it makes > no sense for people to have to download a German build, an English build, > etc. People should be able to post install all localizations, shouldn't > they? > > Pehaps we should be splitting installation approaches completely based on > platforms, WIN users may expect something very simialr to what exists now. > Mac OSX might want to use a similar graphical approach as well albeit > looking differently, Linux may want to use dpkg, and rpm based approaches, > and Solaris, Irix, etc may have different ideas. This would be very nice. A graphical installer is suitable for a Win-System or even a single-user unix installation. But for most Unix-Administrators the common 3-Step-Way (configure, make, make install) is very comfortable. And even usable if you have only access to a non-graphical console. > > Either way, we need to rethink how installation is done in general and > perhaps have platform-centric installers built as part of the OOo build > process. > > Comments, Ideas, rants, and Raves all welcome? > > Hamburg developers, what are your long term plans for installation > approaches? > > What do people think? > > Kevin -- Heute ist nicht alle Tage, ich komm' wieder, keine Frage!!! Joerg BOFH excuse #137: User was distributing pornography on server; system seized by FBI. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to oo-deb/debian/patches by haggai
Repository: oo-deb/debian/patches who:haggai time: Wed Jul 17 19:17:16 UTC 2002 Log Message: It seems this patch is still needed Files: added: 016_zlib_include_linking_fix.diff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to oo-deb/debian/scripts by haggai
Repository: oo-deb/debian/scripts who:haggai time: Wed Jul 17 18:07:23 UTC 2002 Log Message: Move to 1.0.1 upstream tarball Files: changed:vars -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to oo-deb/debian/patches by haggai
Repository: oo-deb/debian/patches who:haggai time: Wed Jul 17 18:07:23 UTC 2002 Log Message: Move to 1.0.1 upstream tarball Files: removed:016_ppc_bridge_fix.diff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to oo-deb/debian by haggai
Repository: oo-deb/debian who:haggai time: Wed Jul 17 18:07:23 UTC 2002 Log Message: Move to 1.0.1 upstream tarball Files: changed:changelog -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to oo-deb/debian by haggai
Repository: oo-deb/debian who:haggai time: Wed Jul 17 18:01:36 UTC 2002 Log Message: Remove old files Files: removed:openoffice.org-common.dirs openoffice.org.undocumented -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to oo-deb/debian by haggai
Repository: oo-deb/debian who:haggai time: Wed Jul 17 18:00:49 UTC 2002 Log Message: Add manpages and fix Lintian warnings. Thanks, Rene! Files: changed:README.Debian changelog rules added: openoffice.org.manpages -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to oo-deb/debian/local/man by haggai
Repository: oo-deb/debian/local/man who:haggai time: Wed Jul 17 17:44:56 UTC 2002 Log Message: Add manpages, thanks to Rene Engelhard Files: added: oocalc.1 oodraw.1 ooimpress.1 oomath.1 oopadmin.1 oowriter.1 openoffice.1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to oo-deb/debian/local/man by haggai
Repository: oo-deb/debian/local/man who:haggai time: Wed Jul 17 17:44:16 UTC 2002 Log Message: Directory /cvs/debian-openoffice/oo-deb/debian/local/man added to the repository Files: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
lintian-fixes / manpages
Hi, here are the fixes for the lintian errors including manpages. Please apply the patch. Regards, Rene diff -urN debian.orig/local/scripts/fixperms.sh debian/local/scripts/fixperms.sh --- debian.orig/local/scripts/fixperms.sh Thu Jan 1 01:00:00 1970 +++ debian/local/scripts/fixperms.shWed Jul 17 18:02:11 2002 @@ -0,0 +1,17 @@ +#!/bin/sh +# script to tidy up to get the permissions in the package right to +# get the package itself lintian-clean + +for i in `find . -type f -name "*.xpt"`; do + chmod ugo-x $i +done +for i in `find . -type f -name "*.js"`; do + chmod ugo-x $i +done +for i in `find . -type f -name "*en_US*"`; do + chmod ugo-x $i +done +for i in `find . -type f -name "*.pl"`; do + chmod ugo+x $i +done + diff -urN debian.orig/oopadmin.1 debian/oopadmin.1 --- debian.orig/oopadmin.1 Thu Jan 1 01:00:00 1970 +++ debian/oopadmin.1 Wed Jul 17 15:33:54 2002 @@ -0,0 +1,26 @@ +.TH oopadmin "1" "April 2002" "OpenOffice.org 1.0.1" "User Commands" +.SH NAME +oopadmin \- Admin tool for OpenOffice.org to add printer and fonts +.SH SYNOPSIS +.B spadmin +.SH DESCRIPTION +oopadmin is a tool belonging to the OpenOffice.org office suite. + +With oopadmin, you can tune some options for OpenOffice.org. +Even as a "normal" user, you can add fonts which should be used by +OpenOffice.org and you can add a new printer or tune your printer +configuration. + +After doing that, OpenOffice.org has to be restarted to let the +settings take effect. + +You also can print a test page to test if your printer configuration +is working. + +.SS "Generic options:" +There are no command line options +.SH SEE ALSO +.BR openoffice (1) +.SH AUTHOR +This manual page was created newly by Rene Engelhard +<[EMAIL PROTECTED]> for the Debian GNU/Linux Distribution, because the original package does not have one. diff -urN debian.orig/openoffice.1 debian/openoffice.1 --- debian.orig/openoffice.1Thu Jan 1 01:00:00 1970 +++ debian/openoffice.1 Wed Jul 17 15:34:05 2002 @@ -0,0 +1,33 @@ +.TH openoffice "1" "April 2002" "OpenOffice.org 1.0.1" "User Commands" +.SH NAME +openoffice \- wrapper script to start OpenOffice.org +.SH SYNOPSIS +.B openoffice +.SH DESCRIPTION +OpenOffice.org is a fully featured office suite for the daily use with all features you'd normally expect in a office suite. + +This script runs OpenOffice with the arguments given on the command line + +There are also some wrapper scripts in /usr/bin: +.TP +oocalc +.TP +oodraw +.TP +ooimpress +.TP +oomath +.TP +oowriter + +which are calling the "normal" openoffice script and runs the wanted OpenOffice.org module + +.SS "Generic options:" +.TP +\fB\fB +These args are passed directly to the real start binary. It mostly contains the file name which should be opened directly with starting OpenOffice.org. +.SH SEE ALSO +.BR oopadmin (1) +.SH AUTHOR +This manual page was created newly by Rene Engelhard +<[EMAIL PROTECTED]> for the Debian GNU/Linux Distribution, because the original package does not have one. diff -urN debian.orig/rules debian/rules --- debian.orig/rules Wed Jul 17 14:49:35 2002 +++ debian/rulesWed Jul 17 15:38:00 2002 @@ -422,6 +422,11 @@ install -m755 debian/local/ooffice debian/openoffice.org/usr/bin/openoffice install -m755 debian/local/spadmin debian/openoffice.org/usr/bin/oopadmin + install -m755 -D openoffice.1 \ + debian/openoffice.org/usr/share/man/man1/openoffice.1 + install -m755 -D oopadmin.1 \ + debian/openoffice.org/usr/share/man/man1/oopadmin.1 + # Remove packaging prefix from configuration files # and set default install directory to ~/.openoffice/ for FILE in program/instdb.ins \ @@ -501,14 +506,24 @@ dh_testroot dh_installdocs - dh_undocumented + dh_installman dh_installchangelogs dh_installmime dh_installmenu dh_link dh_strip dh_compress + ln -s openoffice.1 debian/openoffice.org/usr/share/man/man1/oocalc.1.gz + ln -s openoffice.1 debian/openoffice.org/usr/share/man/man1/oodraw.1.gz + ln -s openoffice.1 \ + debian/openoffice.org/usr/share/man/man1/ooimpress.1.gz + ln -s openoffice.1 debian/openoffice.org/usr/share/man/man1/oomath.1.gz + ln -s openoffice.1 \ + debian/openoffice.org/usr/share/man/man1/oowriter.1.gz dh_fixperms + # after dh_fixperms, there are some wrong permissions left, so we + # fix them ourselves :) + /bin/sh debian/local/scripts/fixperms.sh dh_installdeb dh_shlibdeps ifeq "$(ARCH)" "powerpc"
Re: Desktop integration for distributions [was debian-openoffice Announcing OpenOffice.org 1.0.1]
Hi Chris, Thanks for your reply. There just has to be a better way than having every distribution and OOo itself doing something different which will make support and upkeep unmanageable. Let's think about the very basics for a second (go back to first principles) and see if there is some common ground we can use: 1. Where exactly under Linux should OpenOffice.org be installed? Are there official guidelines? Is this /opt or /usr/bin or what? Does this differ from distribution to distribution? What about other Unix (Solaris, FreeBSD, MacOSX, etc? 2. More specifically, where should all of the pieces of OpenOffice.org be installed? Are there specific directories ... /usr/share/ and /etc/ ... that we could all agree on and what goes there. To help guide this discussion, could you tell me where you put the various pieces of OOo in your latest Debian versions (including workstation pieces)? Perhaps someone from Mandrake could add their info as well. I heard that OOo was part of the alpha RedHat releases as well. Does anyone know where they are placing the pieces. 3. What additional pieces would augment or help OOo under Linux (and other Unixes)? - fonts - ghostscript urw fonts - any ttf free fonts around? - templates, HowTo's etc How / where would these be installed? 4. How does Debian currently handle localizations for languages? it makes no sense for people to have to download a German build, an English build, etc. People should be able to post install all localizations, shouldn't they? Pehaps we should be splitting installation approaches completely based on platforms, WIN users may expect something very simialr to what exists now. Mac OSX might want to use a similar graphical approach as well albeit looking differently, Linux may want to use dpkg, and rpm based approaches, and Solaris, Irix, etc may have different ideas. Either way, we need to rethink how installation is done in general and perhaps have platform-centric installers built as part of the OOo build process. Comments, Ideas, rants, and Raves all welcome? Hamburg developers, what are your long term plans for installation approaches? What do people think? Kevin On July 17, 2002 10:49, Chris Halls wrote: > On Wed, Jul 17, 2002 at 08:04:32AM -0400, Kevin B. Hendricks wrote: > [quoting my announcement of upcoming .deb packages for OOo 1.0.1] > > > > These will include the desktop > > > integration, which is now complete for KDE and possibly for Gnome > > > (but untested). > > > > Are the above in any form to be contributed back to OOo? I would love > > to fix desktop integration for all distributions. > > I wish I could say otherwise, but unfortunately the changes I made all > take place after the network install is complete and the .deb is built. > There are a number of issues with the original install which make it > difficult for me to provide changes that are useful unless decisions are > made to change the way things are done, and that would probably > modifications to the build system. I'll list them here and my thoughts > about them aaybe we can come up with a solution that helps everyone. > > 1. The network install is all to one subtree. > > I fully understand that there are good reasons for doing this (keeping > all files together, making them easy to manage, allowing co-existing > versions, OS-independent layout etc.), but when building packages that > use the OS's package tools such as dpkg or rpm that integrate tightly > with the rest of the system, we need to place files in different places. > For example, to get the desktop icons and shortcuts working for KDE, I > performed a network install to a temporary directory and then moved the > subtrees around: > > share/kde/net/mimelnk/share/icons -> usr/share > share/kde/net/mimelnk/share/mimelnk/application -> usr/share/mimelnk > share/kde/net/applnk -> usr/share > > After that I used sed to edit the pathnames in the shortcuts to point to > the right places. > > The only solution I can think of at the moment is for some extra options > to configure, such as --with-kde-path and --with-gnome-path or something > similar, which can be specified at package build time to allow placement > of these files outside of the main install tree. > > 2. There are only two options for the desktop integration: on or off. > > Our very first packages used the 'on' option: The files were installed > in central locations but also copied to every user's home directory. > This is unecessary if a central install has been performed well, and the > integration is already available centrally. We often had users being > confused by error messages where files could not be copied to ~/.kde2 > (The Debian default is ~/.kde) or ~/gnome, and the files would be left > behind if the user uninstalled the network install without first running > setup in their home directory. After that I switched to 'off', where > the files were not available at all, and the users' co
Desktop integration for distributions [was debian-openoffice Announcing OpenOffice.org 1.0.1]
On Wed, Jul 17, 2002 at 08:04:32AM -0400, Kevin B. Hendricks wrote: [quoting my announcement of upcoming .deb packages for OOo 1.0.1] > > These will include the desktop > > integration, which is now complete for KDE and possibly for Gnome (but > > untested). > > Are the above in any form to be contributed back to OOo? I would love to > fix desktop integration for all distributions. I wish I could say otherwise, but unfortunately the changes I made all take place after the network install is complete and the .deb is built. There are a number of issues with the original install which make it difficult for me to provide changes that are useful unless decisions are made to change the way things are done, and that would probably modifications to the build system. I'll list them here and my thoughts about them aaybe we can come up with a solution that helps everyone. 1. The network install is all to one subtree. I fully understand that there are good reasons for doing this (keeping all files together, making them easy to manage, allowing co-existing versions, OS-independent layout etc.), but when building packages that use the OS's package tools such as dpkg or rpm that integrate tightly with the rest of the system, we need to place files in different places. For example, to get the desktop icons and shortcuts working for KDE, I performed a network install to a temporary directory and then moved the subtrees around: share/kde/net/mimelnk/share/icons -> usr/share share/kde/net/mimelnk/share/mimelnk/application -> usr/share/mimelnk share/kde/net/applnk -> usr/share After that I used sed to edit the pathnames in the shortcuts to point to the right places. The only solution I can think of at the moment is for some extra options to configure, such as --with-kde-path and --with-gnome-path or something similar, which can be specified at package build time to allow placement of these files outside of the main install tree. 2. There are only two options for the desktop integration: on or off. Our very first packages used the 'on' option: The files were installed in central locations but also copied to every user's home directory. This is unecessary if a central install has been performed well, and the integration is already available centrally. We often had users being confused by error messages where files could not be copied to ~/.kde2 (The Debian default is ~/.kde) or ~/gnome, and the files would be left behind if the user uninstalled the network install without first running setup in their home directory. After that I switched to 'off', where the files were not available at all, and the users' complaints changed from 'what are all these file copy errors' to 'where have the menu entries gone'. Gwenole Beauchesne at Mandrake came up with the idea to set INSTALLED=NO in instdb.ins using perl after the network install was complete. But that is really a hack and needs do be an install option so that anyone who performs a network install can enable central integration but disable the modifications to the users' home directory. There has been discussion about this at Issue #6218. 3. The icons are delivered as xpms, but KDE/Gnome expect pngs. In fact, xpms can still be used but support is likely to be dropped at some point. > Also, there is some talk upstream of building a generic GPL installer that > will be run automatically after OOo official install is complete and > install lots of dictionaries, fonts, templates, how-tos, hyphenation > dictionaries, thesauri (or is that thesauruses?) and even handle desktop > integration and allow users to select themes or icon sets. and etc. It > will be able to download all components from the web or use local storage > (harddisk or cdrom). > > The basis for this already exists in the form of the current dictionary > autoinstallers. > > Is there any interest from Debian in getting involved in such a project? > Would it help or hurt your efforts? I'm afraid that a large part of the functionality would be redundant for distribution .deb and .rpm packagers. We already have a centralised, systemwide way of downloading and installing extra software, with all of the infrastructure needed to support mirroring, upgrades, version compatibility etc. The only part which I can see being of interest is the way in which the installed module is made available to the users. But the new central dictionary system in OOo, even this is trivial to do with a simple perl script that adds the appropriate line to the central dictionary.lst. Rene Engelhard made packages for the German dictionaries, so he may be in a better position to comment. If the installer could be used in a scripted update-configuration mode, it may be useful nonetheless. Generally, you only tend to see installers packaged up for Debian if the installed software is not freely distributable (such as the MS truetype fonts or realplayer), or changes so quickly that the packagers and/or infrastruct
Re: Announcing OpenOffice.org 1.0.1
Hi Chris, > These will include the desktop > integration, which is now complete for KDE and possibly for Gnome (but > untested). Are the above in any form to be contributed back to OOo? I would love to fix desktop integration for all distributions. Also, there is some talk upstream of building a generic GPL installer that will be run automatically after OOo official install is complete and install lots of dictionaries, fonts, templates, how-tos, hyphenation dictionaries, thesauri (or is that thesauruses?) and even handle desktop integration and allow users to select themes or icon sets. and etc. It will be able to download all components from the web or use local storage (harddisk or cdrom). The basis for this already exists in the form of the current dictionary autoinstallers. Is there any interest from Debian in getting involved in such a project? Would it help or hurt your efforts? Thanks, Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
fwd: [announce] Announcing OpenOffice.org 1.0.1
So, upstream have announced 1.0.1 officially at last. There were no changes that affected us directly (the last showstopper was related to international installs on Windows), so the 1.0.1rcX .debs that are already available from the unstable source have the same code as the official 1.0.1. We'll be building and uploading new packages based on the official 1.0.1 sources over the next day or two. These will include the desktop integration, which is now complete for KDE and possibly for Gnome (but untested). We will upload to main once these tasks are done: - Fix remaining Lintian errors (Rene Engelhard) - Generate libstlport4.5 .debs compiled with GCC3.0/1 (Jan-Hendrik Palic) - Use free JDK (Peter Novodvorsky) If the first two tasks are complete a long time before Peter is ready, an upload to contrib may take place first. Chris - Forwarded message from Sander Vesik <[EMAIL PROTECTED]> - Date: Wed, 17 Jul 2002 11:57:49 +0100 (BST) From: Sander Vesik <[EMAIL PROTECTED]> Subject: [announce] Announcing OpenOffice.org 1.0.1 To: discuss@openoffice.org, users@openoffice.org, dev@openoffice.org, announce@openoffice.org, dev@marketing.openoffice.org Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm Reply-To: announce@openoffice.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none version=2.31 X-Spam-Level: I am glad to announce the availability of Openoffice.org 1.0.1, the first bugfix release for OpenOffice.org 1.0 New in this release are: * upgrade of the mozilla integration from 0.9.5 to 1.0 * inclusion of a .pdf installation guide in the package * several fixes to font handling code * improved portability * improvements to handling of locales * and numerous other minor bugfixes The OpenOffice 1.0.1 release is from the OpenOffice.org stable branch (OOO_STABLE_1) and work on bugfixing, portability and small incremental improvements will continue on it towards future 1.0.x releases. OpenOffice.org 1.0.1 is available for download from http://www.openoffice.org/dev_docs/source/1.0.1/index.html - End forwarded message - pgpPGxSBWu0y3.pgp Description: PGP signature
cvs commit to oo-deb/debian by haggai
Repository: oo-deb/debian who:haggai time: Wed Jul 17 11:41:27 UTC 2002 Log Message: - KDE integration seems to work well now: Menu entries work, and right click -> Open in Konqueror works too. - Change default user directory to be ~/.openoffice/1.0.1 even if setup is started by hand - Add links in /usr/bin for oocalc, oodraw etc. to /usr/bin/openoffice, and change the wrapper to look at how it was called - Rename /usr/bin/spadmin to ooadmin - Update Debian menu entries with new command names and icon locations - Add some dependencies for debian/rules install target Files: changed:changelog openoffice.org.install openoffice.org.links openoffice.org.menu openoffice.org.undocumented rules -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to oo-deb/debian/local by haggai
Repository: oo-deb/debian/local who:haggai time: Wed Jul 17 11:41:27 UTC 2002 Log Message: - KDE integration seems to work well now: Menu entries work, and right click -> Open in Konqueror works too. - Change default user directory to be ~/.openoffice/1.0.1 even if setup is started by hand - Add links in /usr/bin for oocalc, oodraw etc. to /usr/bin/openoffice, and change the wrapper to look at how it was called - Rename /usr/bin/spadmin to ooadmin - Update Debian menu entries with new command names and icon locations - Add some dependencies for debian/rules install target Files: changed:ooffice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to oo-deb/debian by haggai
Repository: oo-deb/debian who:haggai time: Wed Jul 17 09:07:49 UTC 2002 Log Message: - Include extra files installed with desktop integration (gnomeint,fromtemplate) - gnomeint is in -bin, so update dependencies - Fix typo in kde mimelnk pathname Files: changed:control control.in openoffice.org-bin.install openoffice.org.install -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
