Hi, I just uploaded a(nother) new setup-1.7.exe to install Cygwin 1.7.
You can find it here: http://cygwin.com/setup-1.7.exe The version number is 2.606. The SHA1 checksum is 2df4b76fbff6a1279aecdac342de67d291175560 New features: - Now additionally reads /etc/fstab if it can find it. Features already in 2.605: - Installs 1.7 on NT and 1.5.x on 9x. As far as NT is affected: - Uses long path names and the Cygwin UNICODE transformation of special DOS characters. This should allow to install files with special DOS chars (foo:bar, a<b), as well as files with names consisting of DOS device names (nul.exe, aux.c). - Setup will still look for an old install by searching the 1.5.x registry mount points. If you don't change to another dir in the "Choose Installation Directory" dialog, it will perform an upgrade rather than a fresh parallel install. So, please change the root directory to something like, say, C:\cygwin-1.7 - Reads package DB the first time *after* the user pressed the "Next" button in the "Choose Installation Directory" dialog, so that setup doesn't use the package DB from a former installation by accident if the user chooses to install into a new directory. This only works once! If you press the "Next" button in the "Choose Installation Directory" dialog before you changed the root directory, then press the "Back" button, it's too late. In that case, press "Cancel" and restart Setup-1.7. I couldn't figure out how to drop the entire package DB in memory so that it can be re-read when the directory gets changed by the user. Can somebody help coding this? - Does not write registry mount points anymore. - Dynamically changes the layout of the "Choose Installation Directory" dialog so that there's no user choice for text/binmode. Other changes: - Silently skip empty tar packages of the 46 byte type (for instance gcc-3.4.4-3). - New command-line option which was already present in Dave's test release 2.602: -P --packages Specify packages to install Perhaps I screwed something up with my patches which worked before, but it worked fine for me, so I don't know. Please give it a try and report back. Have fun, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
