Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
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 <cgf AT cygnus DOT com>
Date: Tue, 6 Jun 2000 22:34:06 -0400
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Eliminating usr/i686-pc-cygwin
Message-ID: <20000606223406.A3865@cygnus.com>
Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com
Mail-Followup-To: 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.2i

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'm probably partial to 2.

The rationale for doing this is that some (broken?) configurators look
in /usr/include for specific header files and get confused when they
don't find anything there.

This will probably cause some pain in the short run but I think it is
worth it to make things look more like a normal UNIX system.

Thoughts?

cgf