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





------- Additional comments from [EMAIL PROTECTED] Sat Nov 24 20:10:29 +0000 
2007 -------
vg asked me some days when Issue 83414 would be fixed. For the record, here my
reply (I agreee that the TMP change is completely bogus):

--- snip ---
Date: Wed, 21 Nov 2007 20:33:16 +0100
From: Rene Engelhard <[EMAIL PROTECTED]>
To: Vladimir Glazounov <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: issue 83414: how soon?
User-Agent: Mutt/1.5.17 (2007-11-01)

Hi,

Vladimir Glazounov wrote:
> while working on #81911# I intoduced a check for TMP variable in the build
> tool. Actually, it is right so, but because of missing fix for #83414# we

Wanna know the truth? I think this check is *COMPLETELY NONSENSE*. (And
AFAIS RĂ¼diger and Pavel do, too). (CCed)

Do you also patch any app out there to not set sane defaults for TMP but
require the user to set TMP and not working otherwise?
Or do you just override the envvar and the app will honour that you
want it something else?

The solution would be: restore the build tools old behaviour and let
people override it via envvar (yes, this works) when they want it
somwehere else?

> got problems with build bots - the build tool just refuses to work further
> without $TMP set.

Wheee. Well, you broke it. Even with 83414 "fixed" you still would have
the same problem as this issue ist just about "do not unset TMP/TEMP".
Not setting tmp to something. And even if that worked (see my try ...)
you *STILL* would not have TMP/TEMP set in the env. Plain Debian:

$ env | grep TMP
$ env | grep TEMP
$

What do you expect me to do? Hardcode TMP/TEMP to /tmp? What should I
harcode it for Windows then? Or Mac OS? Or OS/2?


> I see only quick-and-dirty solution for this problem now, that is restore
> the build tool old behaviour. But I would like to see the current
> implementation as soon as 83414 comes.
> Can you tell me your plans about the fix?

Yes. You should revert to something sane.

Regards,

Rene
--- snip --

vg: and your claim that configure unsets TMP is *wrong*. See comment #4 in Issue
83414. Even if we now changed this to TMP in the second line, the stuff will
still be not set because (see above) T(E)MP is not normally defined in a system.
And hardcoding it to /tmp or c:\temp or whatever is even more bogus.

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