This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-67
- From: Robert Pendell <shinji at elite-systems dot org>
- To: cygwin at cygwin dot com
- Date: Mon, 30 Nov 2009 11:23:23 -0500
- Subject: Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-67
- References: <4B13CB3A.firstname.lastname@example.org>
On Mon, Nov 30, 2009 at 8:40 AM, Angelo Graziosi wrote:
> Ken Brown wrote:
>> Nevertheless, it's somewhat startling to see permissions change as a side
>> effect of patching a file. One simple way to prevent this is to unset TMP
>> and TEMP in /etc/profile. Is there any downside to doing this? A search of
>> the mailing list archives shows that the default /etc/profile used to do
>> this. I didn't dig long enough to find out why it changed.
> For the moment, I have added 'export TMP=/tmp' to .bashrc, which works.
> Alternatively, on should use 'TMP=/tmp patch...'
I guess a side question here is if TMP does not exist then should it
be defaulting to the system wide TEMP variable, the one defined in
.bashrc for the user or should it even be created at all? I posted an
strace and it shows TEMP set to /tmp but patch still uses TMP instead
and since TMP doesn't exist it looks like cygwin sets TMP to the
system wide one by default. On linux patch uses whatever TEMP is set
to and doesn't use TMP if it isn't set. If I set TMP then it uses
that instead so it has an obvious preference to it.
The linux distribution was Debian or a close derivative. I don't
maintain the server I tested on.
P.S. - On linux (when I tested) TEMP, TMP, and TMPDIR were not set and
patch defaulted to /tmp.
"A perfect world is one of chaos."
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple