This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated: Cygwin 2.2.0-1
- From: Warren Young <wyml at etr-usa dot com>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Tue, 4 Aug 2015 12:14:37 -0600
- Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.2.0-1
- Authentication-results: sourceware.org; auth=none
- References: <announce dot 20150803131950 dot GA18878 at calimero dot vinschen dot de> <55BFB64C dot 1010802 at towo dot net> <20150803192940 dot GA19315 at calimero dot vinschen dot de> <loom dot 20150804T094839-714 at post dot gmane dot org>
On Aug 4, 2015, at 1:50 AM, Achim Gratz <Stromeko@nexgo.de> wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
>> It's ignored as $HOME in the Cygwin DLL. It's apparently not ignored in
>> the base-files package, but that's another problem.
> ...to which the possible solutions are:
> 1. Not hand a botched HOME environment variable to Cygwin processes.
When you speak of this in terms of processes, I think you mean that the Cygwin DLL would need to filter the environment, which sounds heavy-handed.
If you mean that /etc/profile and such will do the filtering, that could work.
> 2. Do the same checks as the Cygwin DLL and fall back to some more sensible
> default if HOME is botched.
This isnât a second option, itâs an implementation design for option 1.
> 3. Ignore the issue.
Hereâs an interesting experiment to try on your non-Cygwin POSIX boxes:
$ HOME=/dfjkshkds bash -l
$ echo $HOME
Guess what it prints.
Hint: It isnât the second-to-last field in /etc/passwd. :)
Spoiler: Apparently Cygwin is already doing the standard thing.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple