Thanks for the response, If not tar.gz, I should be able to get the unpackaged product, which I can simply copy it over to the destination. In fact this is what I was expecting. I have built a BLFS system following the instructions in the BLFS Book. As per the instructions in the book, once the build is complete, the contents of instsetoo_native/unxlngi6/OpeOffice are simply copied over to /opt/OpenOffice-2.0.3 followed by the icons to /usr/share/icons. Then, OpenOffice should work just like the way it should ! I have failed to understand why this didn't happen in my case. I don't get the OpenOffice directory unless I enable epm. When I enable epm, what is delivered to the directory OpenOffice is useless.
I'm trying hard to know where is the packaging script located so, I can read the script and modify it to deliver it in tar.gz format. There's got to be a list file which would list all the files that need to be installed along with the relative paths (and the directory hierarchy). If I can find that file, its fairly easy to proceed. I can write a script to read the list file and copy the appropriate file from solver to the appropriate directory. I don't know where to look for. My guess is that, the list is dynamically generated from several list files sprinkled throughout the source tree. If I only could get the naming style used for the list files..... Failing that, If it is possible to generate an "archive" or "installed" package from the (SRC680 milestone m188 and newer), I can download that same version and compile. I couldn't get a link to that on the openoffice.orgwebsite. I could see the link to 2.0.4 Release Candidate 3 and I'm not sure if this is what you are talking about. What is the guarantee that, if I install rpm on my system just for this purpose, openoffice-2.0.3 will deliver it in rpm format for sure ? Could it be possible that, what is delivered is again useless as in the case of epm which I already have tried !!? Thanks for the suggestions and I would appreciate if I could be lead in a direction that will get the OpenOffice delivered in some format. I mean a finished product that can be installed with all the features enabled ! Kevin On 11/9/06, Rüdiger Timm <[EMAIL PROTECTED]> wrote:
Kevin Williams wrote: > I have been trying to compile and install Open Office 2.0.3 on BLFS system > using gcc-4.1.1. > > The first time I tried it balked out on epm. As I have epm > installed, open office setup tried to package it with epm and epm > complained about the package name having characters other than letters > and numbers !! > > I cleaned up the source tree and recompiled by specifying --disable-epm and > compiled it with in tree mozilla. It compiled successfully. Now, when I > want > to installit, I see that there's no directory named OpenOffice under > instsetoo_native/unxlngi6 !! Now at this stage I really don't know how to > proceed. BLFS doesn't use any package management system. Hence, I expected > OpenOffice build to create a directory structure and leave all the > necessary > files in there which, I could simply copy over to the destination and it > would > just wor from there ! > > [...] Hi Kevin, AFAIK for OpenOffice.org 2.0.3 there was no simple way to create something like a tar.gz file of the product. Only packages as .deb or .rpm for linux or .pkg for solaris were supported. Meanwhile (SRC680 milestone m188 and newer) we seem to have what you are loking for. In a mail to [email protected] from 10/16/2006 Ingo wrote > in src680 m188 (after integration of cws native62) packing is possible with two new formats: > > "archive" and "installed" > > "archive": The installation set is packed as zip (Windows) or tar.gz(Non-Windows). > "installed": You get an already installed Office product. > > The key for this new kind of installation set, is the environment variable PKGFORMAT (already supported values for PKGFORMAT are "rpm", "pkg", "deb", ...). > > You can set the value of PKGFORMAT to "archive" and/or "installed" in your shell or you can use it only for the current command on the command line (for example in "instsetoo_native/util"): > > "dmake openoffice_de PKGFORMAT=installed" > > Attention: The installation sets are not complete. For example the system integration is missing. Unfortunately I do not have an idea what would be the best way foy you to proceed as you are on (old) OOo 2.0.3. It probably is no solution to wait until December and switch to OOo 2.1 having the new possibility, is it? Perhaps you should ask at [EMAIL PROTECTED], there a re the experts for this kind of questions. Rüdiger --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
