This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: x86/ -> ./ symlink
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 03 Jul 2013 20:49:09 +0200
- Subject: Re: x86/ -> ./ symlink
- References: <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> <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>
Christopher Faylor writes:
> I don't think that anyone was saying that we want one setup.ini to be
> able to handle both distributions though. That certainly isn't the way
> that I've been slowly setting things up on sourceware.org. And, maybe
> more importantly, I don't like the idea so I'm not apt to implement this
> in upset or setup.
Good, that closes the discussion as far as I'm concerned.
> 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.
That'd work for me. These days it's probably far less useful to know
which mirror you downloaded from and more useful to be able to switch to
a different mirror without having to remember that you also need to
rename the existing directory in case you don't want to download all
files again.
> setup.exe would only look in the architecture directory that it cared
> about for setup.ini, ignoring the other architecture.
OK.
> 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. Unfortunately, I don't know who is
> relying on it.
Everybody currently using Cygwin in conjunction with Ports, I'd think.
You could interpret this either as having parallel cache directories or
as a cache directory with the first level anything other than x86*, but
anyway I'd suggests that setup.exe still needs to support it one way or
the other.
> Maybe we could keep a setup-legacy.exe around for a while
> for people who still need this IMO brain-dead behavior. Or, better, tag
> CVS and let them build the source themselves if they need this.
I've been building my own setup.exe for some time, but I don't really
think this is something done oftenâ
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs