This is the mail archive of the
mailing list for the Cygwin project.
Re: x86/ -> ./ symlink
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Tue, 2 Jul 2013 11:28:49 +0200
- Subject: Re: x86/ -> ./ symlink
- References: <20130630223132 dot GA5077 at ednor dot casa dot cgf dot cx> <20130701092301 dot GD2000 at calimero dot vinschen dot de> <20130701111532 dot GA20414 at calimero dot vinschen dot de> <20130701114624 dot GE2000 at calimero dot vinschen dot de> <20130701125056 dot GF2000 at calimero dot vinschen dot de> <20130701151815 dot GA4763 at calimero dot vinschen dot de> <20130701164017 dot GB4763 at calimero dot vinschen dot de> <87li5qdxdp dot fsf at Rainer dot invalid> <20130701180225 dot GC4763 at calimero dot vinschen dot de> <87hagedrdu dot fsf at Rainer dot invalid>
- Reply-to: cygwin-apps at cygwin dot com
On Jul 1 21:14, Achim Gratz wrote:
> Corinna Vinschen writes:
> >> The change itself breaks a few cases that maybe aren't supported,
> >> but nevertheless worked for quite some time.
> > What cases?
> I have abandoned this directory layout some time ago, but I was doing
> things like
> with normally a single setup.ini in each subtree (sometimes a few levels
> down) and it would integrate all the setup.ini it found depending on
> where I'd start setup.exe or what I told it was the local directory.
> I'm still using a similar layout for keeping track of the mirrors and my
> local packages, but I copy the package files and re-write setup.ini to
> reference them in a single tree somewhere else.
That should still work if you move the setup.ini files in a x86 or
Having said that, I could also change setup so that any setup.ini file
which is not under a $target subdir is still recognized, but only when
trying to install a 32 bit Cygwin. This should make the code backward
compatible with existing layouts.
What do you think? Does that make sense?
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com