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: Wed, 3 Jul 2013 21:06:53 +0200
- Subject: Re: x86/ -> ./ symlink
- References: <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> <20130702092849 dot GA10542 at calimero dot vinschen dot de> <20130702094006 dot GB10542 at calimero dot vinschen dot de> <8738rw20zw dot fsf at Rainer dot invalid> <20130703073701 dot GC5118 at calimero dot vinschen dot de> <87obaj1vmq dot fsf at Rainer dot invalid> <20130703182826 dot GB3182 at ednor dot casa dot cgf dot cx>
- Reply-to: cygwin-apps at cygwin dot com
On Jul 3 14:28, Christopher Faylor wrote:
> What I'm leaning towards doing is creating a new "cache" directory which
> just contains x86 and x86_64 directories with a setup.ini in each. I'd
> get rid of the (IMO) stupid mangled site names since I don't think they
> are really important and just download files directly into x86*/release.
> setup.exe would only look in the architecture directory that it cared
> about for setup.ini, ignoring the other architecture.
Why introducing a new "cache" dir? If you drop the mangled site dir,
you can just store the flattend directory structure below the local
install dir without introducing another directory level (except of the
x86/x86_64 subdirs, of course)
> If it's important than we could have setup do the old stupid way of
> looking up and down in non-"cache" directories for setup.ini but I think
> I'd like to retire that behavior.
There would be no way anymore to support multiple different installation
repositories, as with using cygwin and cygwinports in parallel.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com