Issue 64802 - Non-conflicting SDK gid module name
Summary: Non-conflicting SDK gid module name
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2006-04-26 20:22 UTC by pmladek
Modified: 2013-08-07 15:26 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---

A proposed solution. (754 bytes, patch)
2006-04-26 20:23 UTC, pmladek
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description pmladek 2006-04-26 20:22:22 UTC
I want to build OOo and OOo-sdk packages from single spec file. I use the simple
installer ( -simple) in the %install section. The real call
looks like:

perl -w $SOLARENV/bin/ -f openoffice.lst -l $langs -p
OpenOffice -packagelist ../inc_openoffice/unix/packagelist.txt -addpackagelist
../inc_openoffice/unix/packagelist_language.txt -buildid $BUILD $destdir $strip
-simple $path 

perl -w $SOLARENV/bin/ -f openoffice.lst -l en_US -p
OpenOffice_SDK -packagelist ../inc_sdkoo/unix/packagelist.txt -buildid $BUILD
/var/tmp/OOo-test -dontstrip -simple /usr/lib/ooo-2.0/sdk

The simple installer produces list of files that can be later used in the %files
section. The lists of files are named by the gid module ids. I got into troubles
because both products OpenOffice and OpenOffice_SDK include Module
gid_Module_Root. So, one file list was overwriten.

There are three possibilities how to fix it:

1. I could save the conflicting file list before I install SDK.
2. We could fix the installer to use another names for the file lists.
3. We could rename gid_Module_Root for OpenOffice_SDK.

I like the 3rd solution and prepared a patch for it. It solved the problem for me.

What do you think about the proposed change?
Comment 1 pmladek 2006-04-26 20:23:17 UTC
Created attachment 36075 [details]
A proposed solution.
Comment 2 2006-04-28 16:02:23 UTC
If the third solution works without problems I would prefer it, too. But we will
have to test this for all platforms, especially Windows.
-> setting target OOo 2.0.4 
Comment 3 2006-06-27 13:46:57 UTC
Looking into the packaging process, I found a lot of dependencies to the root
module that is defined by "gid_Module_Root". It would be very dangerous to
change this most important module gid. Besides every product has a module
gid_Module_Root, so that it is not a global solution to fix this for one special
product. Therefore I do not like the patch 36075.  It is not sufficient, that
the lists of files are named by the gid module ids, you also have to include the
product name into this list names.
Comment 4 pmladek 2006-06-27 14:44:08 UTC
OK, I'll create another patch. I will update installer to add the product name
to the list names...

Thanks for you opinion.
Comment 5 pmladek 2006-08-09 18:28:04 UTC
I am sorry. I was somewhat busy. I'll look on it for OOo-2.0.5.
Comment 6 2007-04-10 14:08:09 UTC
Removing issue type PATCH, because currently no valid patch is available.
Comment 7 pmladek 2007-10-01 18:35:43 UTC
I'll look at it together with the other package split work.
Comment 8 grehtietalders 2010-10-23 15:44:14 UTC
Created attachment 72669
Comment 9 pmladek 2013-04-08 08:29:38 UTC
I do not plan to work on this anytime soon => resetting to the default assignee