To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=44853
User cloph changed the following:
What |Old value |New value
================================================================================
Target milestone|OOo 2.0 |---
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Sat Mar 12 09:36:35 -0800
2005 -------
rene: you did not seem to get the point.
>>>On the Debian buildds you are *not* allowed to change anything in $HOME
>>>*except*the buildir, tmp and so on. You you *can't* add a hack like this.
>
>>What does this have to do with rpm?
>>This is not a hack. This is how you configure rpm.
>
>The problem is that we DO NOT have access to the rpm config there.
What is "there"? rpm reads the following files
rpmrc Configuration
/usr/lib/rpm/rpmrc
/usr/lib/rpm/redhat/rpmrc
/etc/rpmrc
~/.rpmrc
Macro Configuration
/usr/lib/rpm/macros
/usr/lib/rpm/redhat/macros
/etc/rpm/macros
~/.rpmmacros
[...]
So you can override whatever is written in the global configuration with files
in your homedirectory.
If debians version of rpm doesn't allow this, then it unusable and very broken
for no reason.
> Yes, but you should not brequire builders to configure their rpm first, this
> can not be done on some systems.
I require the builders to have a working configuration. Whether they need to
configure it first or whether it runs out-of-the-box is irrelevant.
The spec does not require special adaptions. It requires the basic directories
to be accessible.
>> Everyone who ever has sucessfully built a rpm before will be able to build
>> the
>> freedesktop-rpm with exactly the same account.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> (Emphasis on "build" - not "package files from the disk into a rpm")
>This isn't true. I always could build rpms fine on my Debian box - just as
>root.
Why do you think OOo should behave differently then?
> I can configure it to use another dir, but AGAIN, not everyone can do this or
> is allowed to do this.
Everyone can do this. If not, he won't be able to create any rpms.
>>It is not only debian's rpm. It is a general "error" of rpm to have the topdir
>>default to /usr/something. It is the configuration that is broken.
>Right. You should then work around it. See above. This fix *has* to be in m86
>IMHO.
You don't blame OOo when your version of "cp" segfaults. You don't blame OOo
because your unpatched epm cannot create relocatable packges. You don't blame
your system mozilla for not being built with nss support.
But you blame OOo for not fixing the users build-environment? Strange attitude.
>> You cannot build any rpm with your environment. (again: "build", that
>> involves
>> %setup and %build).
>
>I can, if I'm root.
Then why do you expect OOo to be able to build rpms as non-root user?
Again: Fix your configuration. It is a problem of your configuration.<period>
> You normally need root rights anyhow to get the file permissions right. Or how
> do you set permissions if you (and rpm) are not allowed to chmod?
You define it in the %files section using %defattr() or %attr().
Again: You don't need to be root to build /any/ rpms.
When you build debian packages, you tell the build tool where it should put the
extracted files, what directory to use as as installroot, etc.
If you set some of the directories to point to a location that you do not have
write access to then the build will break.
Will you then blame OOo as well for not correcting the misconfiguration in the
debian build system?
Again: The problem is that /your system's configuration of rpm/ tells rpm to use
a directory for which regular users do not have write access.
Insisting on having a workaround for this *misconfiguration of a tool installed
on your system* in OOo's build-system is absurd.
(You have to accept that your system is misconfigured for the purpose of being
able to create packages with your regular account. This is a fact (and this
doesn't exclude that your configuration works /under special circumstances/ -
that is for rpms created by bypassing rpm)
Note that I'm not against specifying the _buildroot on the commandline. But this
should not be done to fix a broken configuration, but to have everything created
somewhere below unxlngi*.
Thus there is no justification for this being a P1. It is a cosmetic issue.
---------------------------------------------------------------------
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]
