Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com X-Authentication-Warning: abomination.cygnus.com: mdejong owned process doing -bs Date: Tue, 11 Apr 2000 23:27:09 -0700 (PDT) From: Mo DeJong To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Testing/Feedback on new setup.exe Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII TESTING THE NEW INSTALLER I copied setup.exe to the directory where the .tar.gz files I downloaded from the ftp site live. The install seems to go fine until I got to the gdb tar file. It spews out a bunch of errors about "Could not create file: Permission Denied", and then tar exits. At that point, the installer thinks things are finished and it startes creating the installed packages list. On a side note, the "Creating the uninstall file...45%" is WAY faster now, nice job Chris. ... /cygdrive/c/Temp/tar: usr/share/iwidgets3.0.0/demos/watch: Could not create file: Permission denied /cygdrive/c/Temp/tar: Error exit delayed from previous errors Creating the uninstall file...45% If tar exits with some error condition, the installer needs to stop and give the user some indication of the package that generate the errors and what they should do next. We could print something like this: "Error installing the gdb-20000127.tar.gz package. You may have a corrupted tar file, or there may be some other problem with your install. Check the README and the FAQ http://sourceware.cygnus.com/cygwin/faq" I tried running tar by hand to reproduce the errors. I was not able to capture the errors printed by setup.exe and they were not logged in the installer.log file. % tar -C / -xzvf gdb-20000127.tar.gz usr/bin/cygitcl30.dll usr/bin/cygitclsh30.exe usr/bin/cygitk30.dll usr/bin/cygitkwish30.exe usr/bin/cygtcl80.dll .... usr/share/tk8.0/tkfbox.tcl usr/share/tk8.0/tkfboxTest.tcl usr/share/tk8.0/xmfbox.tcl /usr/bin/tar.exe: usr/lib/libtcl80.a: Could not create file: Permission denied /usr/bin/tar.exe: usr/lib/libtk80.a: Could not create file: Permission denied /usr/bin/tar.exe: usr/man/man1/itclsh.1: Could not create file: Permission denied /usr/bin/tar.exe: usr/man/man1/itkwish.1: Could not create file: Permission denied /usr/bin/tar.exe: usr/man/man3/Resolvers.3: Could not create file: Permission denied ... /usr/bin/tar.exe: usr/share/iwidgets3.0.0/demos/toolbar: Could not create file: Permission denied /usr/bin/tar.exe: usr/share/iwidgets3.0.0/demos/watch: Could not create file: Permission denied /usr/bin/tar.exe: Error exit delayed from previous errors Something really strange is going on in /usr/lib. If I do a "ls /usr/lib" I can see the files that were installed but if I open the same directory in explorer it does not see the files, the dir just appears empty. I did not see this error with the last installer and it should be the only thing that is different. Was something in the installer changed that would explain this error? I thought I would try to work around the problem by just removing the directory that contained the gdb tar.gz file. That worked in the sense that the installer would install without errors, but I would like to be able to run gdb so it is not a very good fix. I also tried putting the setup.exe file into the "root" dir of the files I downloaded off the ftp site. I downloaded to C:\Temp\cygwin-net-485, so the bash tar file was C:\Temp\cygwin-net-485\bash\bash.tar.gz. I saved the installer to C:\Temp\cygwin-net-485\setup.exe and tried to run it, it puked out these errors. Press to accept the default value. Root directory? [C:\Cygwin] Install from the current directory (d) or from the Internet (i)? [i] d Installing ash.tar.gz Unable to extract "ash.tar.gz": No error Installing bash.tar.gz Unable to extract "bash.tar.gz": No error ... This seems like an error that a user is likely to make, so we really should put a note about this in the README. As a side note, it would be VERY helpful if error messages were actually captured and written to install.log. The errors can be echoed to the console in addition to being written to the log, but not writing them to the log is just a bad idea. We need to be able to tell users "just send us the log" to figure out where the problems are. The "two cygwin dlls" problem that I noticed with the last version of the installer seems to have gone away. Now, only /bin/cygwin1.dll is installed (from cygwin.tar.gz) I also took a look at the README file, it details how to bootstrap a cygwin install in the event you do not have an installer. This file needs to be updated to account for the new install process. If nobody else pipes up saying they want to do it, I can write the new README. We also need a ReleaseNotes file that details the current "known problems" that users are likely to run into. This is a minor issue, but should the name of startup.zip be changed to bootstrap.zip? That might help clear up what the file is actually used for. That of course assumes that we even want to keep it around now that we have an installer. I hope that helps Mo DeJong Red Hat Inc.