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 Message-ID: <20000607130351.10075.qmail@web113.yahoomail.com> Date: Wed, 7 Jun 2000 06:03:51 -0700 (PDT) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: Re: Eliminating usr/i686-pc-cygwin To: cygwin-developers AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Chris Faylor wrote: > I've been perfecting my "mknetrel" script to the point where it is now > easy to eliminate the i686-pc-cygwin directory. > > We've talked about doing this in the past and even, I think, decided that > we would do this for the next net release but we never did this. > > I'm ready to make a cygwin release but I'd like to also make this change. > > I can think of a few ways to do this. > > 1) Setup.exe can issue a warning if it sees this directory, and do nothing. > 2) Setup.exe can issue a warning, and move the directory out of the way. > 3) Setup.exe can issue a warning, and remove the directory. > 4) Setup.exe can do 2) or 3) and do a: 'ln -s usr i686-pc-cygwin'. > I like this plan. I like option 3, this is what I used to do with the b20 directory structure. What happens if for some reason a user has a file with a same name in /usr/include? You probably should warn about overwriting files and ask if a backup has been performed. This would make the need for backup obvious although there is nothing we can do more. Regards, ===== --- Earnie Boyd: __Cygwin: POSIX on Windows__ Cygwin Newbies: __Minimalist GNU for Windows__ Mingw32 List: Mingw Home: __________________________________________________ Do You Yahoo!? Yahoo! Photos -- now, 100 FREE prints! http://photos.yahoo.com