On Jul 2 11:40, Corinna Vinschen wrote: > On Jul 2 11:28, Corinna Vinschen wrote: > > 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 > > > > > > …/mirror/cygwin/ > > > …/mirror/cygport/ > > > …/local/patch/ > > > …/local/packages/ > > > > > > 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 > > x86_64 subdir. > > > > 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. > > Easier said than done. If I change the code to ignore the subdir name > on 32 bit installs, then it will pick up 64 bit setup.ini files, too. > > Bad, bad, bad. > > Given that, I really think the best way to handle this is to use > different ini file names: > > setup-x86.ini -> 32 bit > setup-x86_64.ini -> 64 bit > setup.ini -> allow with 32 bit install for backward compat.
Additional advantage for installing from local dir: We can restrict the recursive search for the ini file to one level, instead of two. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
