This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated: Cygwin 2.2.0-1
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Tue, 04 Aug 2015 20:53:52 +0200
- 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> <895515CC-6BB7-41E7-AEA5-30FBBE071153 at etr-usa dot com>
Warren Young writes:
> 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
Cygwin DLL already does some conversions of the Windows environment. It
could (hypothetically) do a more thorough job and/or sanitize the
environment to make the result more POSIX conformant.
Try defining some Wnidows environment variables that have illegal POSIX
names, for instance.
> 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.
That's the part that involves me changing base-files.
>> 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.
That's why I offered to ignore the issue. That also needs nothing to be
done by me, which is an added benefit. :-)
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple