X-Spam-Check-By: sourceware.org
Message-ID: <40944.84.246.168.11.1160663798.squirrel@mail.morrison.mine.nu>
In-Reply-To: <Pine.GSO.4.63.0610120924170.28291@access1.cims.nyu.edu>
References: <452D2696 DOT 3060602 AT users DOT sourceforge DOT net>     <014c01c6ed5b$d6a1e9a0$a501a8c0 AT CAM DOT ARTIMI DOT COM>     <egjc38$teg$1 AT sea DOT gmane DOT org>     <20061012065523 DOT GP13105 AT calimero DOT vinschen DOT de>     <20061012111836 DOT GA29649 AT trixie DOT casa DOT cgf DOT cx>     <20061012115416 DOT GB8323 AT calimero DOT vinschen DOT de>     <51442 DOT 84 DOT 246 DOT 168 DOT 11 DOT 1160654571 DOT squirrel AT mail DOT morrison DOT mine DOT nu>     <Pine DOT GSO DOT 4 DOT 63 DOT 0610120924170 DOT 28291 AT access1 DOT cims DOT nyu DOT edu>
Date: Thu, 12 Oct 2006 15:36:38 +0100 (BST)
Subject: Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1
From: "John Morrison" <john AT morrison DOT mine DOT nu>
To: cygwin AT cygwin DOT com
Reply-To: john AT morrison DOT mine DOT nu
User-Agent: SquirrelMail/1.4.8
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Thu, October 12, 2006 2:41 pm, Igor Peshansky wrote:
> On Thu, 12 Oct 2006, John Morrison wrote:
>
>> On Thu, October 12, 2006 12:54 pm, Corinna Vinschen wrote:
>> >
>> > I think it is needed.  At least the base-files-mketc.sh postinstall
>> > script creates paths which point outside the Cygwin root, so it either
>> > needs to reference cygdrive paths, or use DOS paths.  Using cygdrives
>> > paths is preferable, IMHO.  Since the cygdrive path is not fixed, and
>> > can even differ between different users on the same machine, there
>> must
>> > be a fixed method to reference these paths.
>> >
>> > Personally I'd rather not further clutter the root directory, which is
>> > why /proc seems to me to be a better place to point to the cygdrive
>> > paths in a constant fashion.  But that is only a mild opposition.  I'd
>> > also go along with /cygdrive.
>>
>> I've changed the script (which I didn't write!) to use cygpath --sysdir
>> which outputs cygdrive paths.  I should be able to get a new release out
>> by the weekend, but I'll hold off until this discussion is decided.
>> Personally I don't mind either an always existing /cygdrive or something
>> in /proc.  Only thing that would ask is; what would cygpath output?
>
> John,
>
> I wrote the script originally, and the initial version did use POSIX
> paths.

I thought you did and was suprised to find it not using POSIX paths but
assumed that there was a reason...

>  I've just re-read the early discussions, and found this:
>
> <http://cygwin.com/ml/cygwin-apps/2003-02/msg00033.html>.

and there it is.

> I think the issue is still valid -- if the installing user has the
> user-level cygdrive prefix set, "cygpath --sysdir" will output something
> that won't work for other users on the machine, and the links will be
> broken.
>
> If we add a standard /cygdrive prefix, we'll also need to change cygpath
> to force that standard prefix for out-of-tree paths (otherwise user and
> system mounts take precedence).  Something like "cygpath -S -s" (or
> "cygpath --sysdir --standard")...
>
> However, if we really want to make this more robust, we'd need something
> like this:
>
> SAVED_CYGDRIVE="`mount -m | grep '^mount -u -[bt] -\?-c'`"
> mount -u -b -c '/cygdrive'
> # Do the path manipulation here
> umount -u -c
> [ -n "$SAVED_CYGDRIVE" ] && eval "$SAVED_CYGDRIVE"
>
> Opinions?

Can you write the new version and I'll just package it? ;)

> 	Igor
> P.S. One annoying thing about /cygdrive is that tab-completion for it is
> annoying OOTB, since there are also /cygwin.bat and /cygwin.ico.  One
> thing I normally do on all new installs is rename those two files to
> /Cygwin.bat and /Cygwin.ico -- since bash uses case-sensitive completion
> by default, this allows /c<Tab> to get to /cygdrive immediately.  Can we,
> perhaps, rename the .bat and the .ico files to start with a capital 'C' on
> new installs?  I'll send a patch to cygwin-apps.

or put them somewhere else...

/etc/setup/Cygwin.bat /etc/setup/Cygwin.ico?  I believe that there's
nothing in the bat file which precludes this and it would hide them away
nicely.

J.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/