On Jul 2 21:52, Achim Gratz wrote: > Corinna Vinschen writes: > >> 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. > > I'm usually for backwards compatibility, however in this case the > current behaviour is largely undocumented and somewhat surprising, so > lets drop the cruft and clearly specify which directory layouts are > expected and supported. > > > 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. > > Yes, that looks nicer to me. Yet another option is to stick with > setup.ini and merge the information into a single file with [x86] and > [x86_64] install sections.
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. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
