X-Spam-Check-By: sourceware.org
Date: Thu, 12 Oct 2006 22:08:20 -0400 (EDT)
From: Igor Peshansky <pechtcha@cs.nyu.edu>
Reply-To: cygwin@cygwin.com
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1
In-Reply-To: <20061012145226.GG8323@calimero.vinschen.de>
Message-ID: <Pine.GSO.4.63.0610122205460.2556@access1.cims.nyu.edu>
References: <452D2696.3060602@users.sourceforge.net>  <014c01c6ed5b$d6a1e9a0$a501a8c0@CAM.ARTIMI.COM> <egjc38$teg$1@sea.gmane.org>  <20061012065523.GP13105@calimero.vinschen.de> <20061012111836.GA29649@trixie.casa.cgf.cx>  <20061012115416.GB8323@calimero.vinschen.de>  <51442.84.246.168.11.1160654571.squirrel@mail.morrison.mine.nu>  <Pine.GSO.4.63.0610120924170.28291@access1.cims.nyu.edu>  <40944.84.246.168.11.1160663798.squirrel@mail.morrison.mine.nu>  <20061012144859.GF8323@calimero.vinschen.de> <20061012145226.GG8323@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Thu, 12 Oct 2006, Corinna Vinschen wrote:

> On Oct 12 16:48, Corinna Vinschen wrote:
> > On Oct 12 15:36, John Morrison wrote:
> > > On Thu, October 12, 2006 2:41 pm, Igor Peshansky wrote:
> > > > 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.
> >
> > So it looks like using mixed paths (cygpath -m) would be an easy way
> > out of this for now.
>
> Naah, scratch that.  Creating a mount point for $SYSTEMROOT seems the
> better solution.

I'll go with mixed case.  The mount point for $SYSTEMROOT will either have
to be explicitly created, or it will need to be built into cygwin1.dll.
In the former case, it's more hassle for the user; in the latter it won't
solve the problem for older cygwin versions.  And if we make it the job of
/etc/postinstall/base-files-mketc.sh, we're depriving the user of a scarce
resource -- a mount table entry (unless we raise the limit, but then again
it won't work for older versions).
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
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/

