At last, success !! Thanks for every one who kept with me all along anf for all that help and tips and suggestions !
Its one of those times when you change something and forget it which, takes you chasing wild goose !! As I had epm installed, dmake tried to make use of system installed epm which resulted in not delivering the package (because, system installed epm did not accept product name containing hyphens and dots) ! To circumvent this problem, I edited the script solenv/bin/modules/install/epmfile.pm and hardcoded the package name as OpenOffice presuming that dmake really was gonna create a single package ! That lead to those problems where I always ended with 1 2.8MB package. Later, I forgot it completely and have been trying to make things happen and came here for help ! Only after, repeated attepmts to make it happen did I realized that, I had hardcoded the package name and that resulted in epm overwriting the same file again and again ! I changed it back to the previous value ($localpackagename variable) and things worked like a charm !! I apologize for the inconvenience and all the trouble I've caused. Sometimes I'm much more than a moron !! ;-) There are these few findings I would like to summarize. Maybe, it will help someone who might fall into the same trap as I did. Maybe, the documentation can be updated to include this scenario. 1. dmake tries to make use of system installed epm if there is one and this leads to nothing as system installed epm (I've installed version epm-4.0) complains of package name having characters other than letters and numbers ! dmake does nothing about it and simply terminates with an error message. In such cases it becomes absolutely necessary to specify --with-epm=internal while running configure. 2. Irrespective of whether epm is installed on the system or not, dmake makes use of epm to package the end product be it in tar.gz or .deb or pkg etc.... 3. Configuring with --with-package-format=installed will fail as dmake uses epm to package and epm will complain that "installed" is not a recognized format. 4. Configuring with --disable-epm will result in dmake building the solver modules and not packaging it further. dmake terminates after building solver modules with a message "No EPM: Do no packaging at this time" !! Ofcourse, the scenario might be different in the later realease. (The above is true for 2.0.3) Now, I've got the package in tar.gz format as well as the scripts. There are 25 packages delivered. When I ran the script openoffice.org-core0.install it entered an infinite loop which resulted in 100s of bash shells being lauched and I'd to kill it. Later, I simply extracted the contents of *.sw files and OpenOffice-2.0.3 works just perfect. I am amazed by the speed it launches. I have OpenOffice installed on a SuSE system and OpenOffice takes ~2 minutes to lauch !! Looks like 4 days of hard work has paid off !! ;-) Thanks again to everyone for all the help. I would really appreciate if above findings could be investigated further and appropriate remarks be included in the documentation. Kevin On 9 Nov 2006 17:52:12 -0000, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=71359 User is changed the following: What |Old value |New value ================================================================================ Assigned to|is |mikkevin -------------------------------------------------------------------------------- ------- Additional comments from [EMAIL PROTECTED] Thu Nov 9 09:52:12 -0800 2006 ------- Please see my blog http://blogs.sun.com/GullFOSS/entry/new_package_formats_for_developers in which I introduce the new package formats "installed" and "archive". I think, this is exactly what you want. There you get installation sets, that are no RPMs and that do not use epm. In this installation sets the system integration packages are missing. But you can copy this installation sets to any place you want. Because your "build" in instsetoo_native fails, you can build without error by using different dmake commands. Please call "dmake" in the directories "packimages" and "inc_openoffice/unix" inside instsetoo_native and then call dmake openoffice_en-US PKGFORMAT=installed in instsetoo_native/util, if you want to create an english OpenOffice.org product, that is already installed. You can copy this or start directly "soffice". You find this product in "instsetoo_native/unxlngi6/openoffice/installed/install/en-US" --------------------------------------------------------------------- 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
