To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=39756





------- Additional comments from [EMAIL PROTECTED] Fri Feb 25 03:38:41 -0800 
2005 -------
> Is there a way to tell rpm to use unique (sub-) directory names for building 
> and installing ?

Yes. simply use the "-n" switch to the %setup macro and it will the directory
with the name specified after -n

If you don't specify -n, the dirname will default to %name-%version (which
collides in your environment).

So use 
"%setup -T -c -n %name-%version-%uniqueID"

and the build will have a unique directory (given the ID you give is unique :-)

For the installation, do the same for the "BuildRoot", e.g. use
"BuildRoot: %_tmppath/%name-%version-build-%uniqueID"

and rpm will put its files under the unique directory when installing. 

Pass rpm the unique id during the build the same way as you pass the version and
the other variables.
"rpmbuild -bb --define "uniqueID <yourID>" specfile

If you do not want to create the files during the build somewhere below the
unxlngi-directories, redefine "_builddir" (as you did with _rpmdir)

To put the files somewhere below unxlngi-directory, define the BuildRoot
accordingly.

HTH.

BTW: what will be the naming of the packages? now there are multiple
core-packages. Will this be the final naming-scheme?
As you may have noticed, I did not update the spec to run
update-desktop-database from within the trigger-script yet. (because I don't
know by what it should be triggered. "openofficeorg-core" does no longer exist)

---------------------------------------------------------------------
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]

Reply via email to