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 From: Chris Faylor Date: Thu, 13 Apr 2000 14:03:25 -0400 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: setup + directories Message-ID: <20000413140325.A13789@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i I added code in the uninstall phase to detect directories and for good measure added things like bin\cygwin.bat, \tmp, \usr\local, \usr\local\lib, and \usr\local\bin to the list of directories which uninst will try to remove. I also added /usr/local/bin to the path, as Mo suggested. The uninstall is still not really robust. If the tar file does not actually create the directory, uninst does not try to remove it. It would be nice to add the intermediate parts of the directory to the list of directories to be deleted if something like /usr/foo/bar/blaz was extracted and /usr/foo and /usr/foo/bar did not exist prior to the extraction. But that's for later, I think. cgf