This is the mail archive of the cygwin-apps mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: x86/ -> ./ symlink

On Wed, Jul 03, 2013 at 06:00:29PM +0200, Achim Gratz wrote:
>Corinna Vinschen writes:
>> Uh, oh.  If you have two different HEAD versions on 32 and 64 bit, how
>> do you express this?  This complicates the setup.ini handling a lot.
>> Personally I'm glad if I don't have to dig too deeply in the weird setup
>> C++ code.
>I've just put it out there if anybody felt strongly negative about
>having two differently named setup.ini files.  It'd work like this:
>--8<---------------cut here---------------start------------->8---
>@ cygwin
>sdesc: "The UNIX emulation engine"
>category: Base
>requires: base-cygwin _autorebase
>version: 1.7.20-1
>install: release/cygwin/cygwin-1.7.20-1.tar.bz2 2658640 537875d7c34a34cfccd827c32689ea99
>source: release/cygwin/cygwin-1.7.20-1-src.tar.bz2 10424531 62b598c6227592557596d41cfa3900ef
>[prev x86]
>version: 1.7.18-1
>install: release/cygwin/cygwin-1.7.18-1.tar.bz2 2647371 d31e415389aee87d8f8ea12055b1371e
>source: release/cygwin/cygwin-1.7.18-1-src.tar.bz2 10402672 5e56caa0ba6b23b5e07b2f055abc3219
>version: 1.7.21-6
>install: x86_64/release/cygwin/cygwin-1.7.21-6.tar.bz2 2069326 2148fbe76a6fa74320b322ccdd02c311
>source: x86_64/release/cygwin/cygwin-1.7.21-6-src.tar.bz2 10572067 adceb03435abae7e7182223ed115fb4d
>[prev x86_64]
>version: 1.7.21-5
>install: x86_64/release/cygwin/cygwin-1.7.21-5.tar.bz2 2069437 8af71520550df186681b5303ef9fdc40
>source: x86_64/release/cygwin/cygwin-1.7.21-5-src.tar.bz2 10568090 e9db7d9c3f645e93c64bed3ace1c900d
>--8<---------------cut here---------------end--------------->8---
>If the architecture is missing, then the entry applies to all of them.

While it wasn't really my goal to allow downloading 64-bit and 32-bit
packages to the same place I thought it was a nice side-effect.  I can
see that, since this is setup.exe, it can never be that easy.

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  And, maybe
more importantly, I don't like the idea so I'm not apt to implement this
in upset or setup.

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.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]