Re: [ANNOUNCEMENT] Updated: Cygwin 2.2.0-1

[Warren Young <wyml@etr-usa.com>]

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
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple