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


User cloph changed the following:

                  What    |Old value                 |New value
================================================================================
                  Keywords|                          |oooqa
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Thu Jul 28 07:26:06 -0700 
2005 -------
> I think the trick is the lower case 'yes', not the quoting.

No, it is as well the name of the variable:
Wrong:    NO_BRP_STALE_SYMLINK
Correnct: NO_BRP_STALE_LINK_ERROR


> However I don't understand why this issue does not also occur with the 
> suse/redhat package(s) - or does it ?

from issue 46226:
| The other menu-packages simply don't use an install stage at
| all, but use dirty makefile-magic 

The symlink-check-script is run as %__os_install_post which is executed after
the %insatll-section of the SPEC. When there is no %install, the script is not
run -> Build doesn't break.

maxweber wrote:
> if you 'export NO_BRP_STALE_LINK_ERROR="yes"' in LinuxIntelEnv.sh the
> build runs fine here on SuSE 9.3

I don't think it is worth to check whether the build-host is SuSE or another
distro. Just export it everytime and you should be fine.

(but I'm not convinced that this is better than adding it to the specfile)

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