This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated: Cygwin 2.2.0-1
- From: Nicholas Clark <nicholas dot clark at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 5 Aug 2015 16:58:01 -0700
- 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> <87wpxac2bj dot fsf at Rainer dot invalid> <20150805075435 dot GP17917 at calimero dot vinschen dot de> <1324339149 dot 20150805194114 at yandex dot ru>
I totally agree that setting HOME to a relative-path is probably a Bad
Idea, and can/should be undefined behavior. As for absolute paths (and
whether they should be POSIX, Windows, or either), that's a little
less cut and dry for me.
I currently use a ton of scripts of the general form:
--------
Cygwin.bat:
@echo off
@pushd %~dp0
@set TOP=%CD%
@popd
set PATH=C:\Windows\SYSTEM32;C:\Windows
@set HOME=%TOP%\home\%username%
@chdir %TOP%\installation\bin
@start mintty.exe -e %TOP%\installation\bin\bash.exe --login -i
exit
--------
for using Cygwin in a user-level installation to my local directory.
It's not a big deal to go through these and update them if Cygwin
loses its ability to interpret Windows-style HOME paths, but there are
probably a lot of users out there who aren't on the mailing list and
wouldn't know that this change was happening until their installations
broke.
So I'm in camp 'leave it as-is', maybe with the exception of
disallowing relative paths. :)
-Nick
--
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