From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-86116-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 23757 invoked by alias); 20 Nov 2003 21:19:44 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 23748 invoked from network); 20 Nov 2003 21:19:44 -0000
Received: from unknown (HELO mailout.TechFak.Uni-Bielefeld.DE) (129.70.136.245)
  by sources.redhat.com with SMTP; 20 Nov 2003 21:19:44 -0000
Received: from xayide.TechFak.Uni-Bielefeld.DE.TechFak.Uni-Bielefeld.DE (xayide.TechFak.Uni-Bielefeld.DE [129.70.137.35])
	by momotombo.TechFak.Uni-Bielefeld.DE (8.11.7p1+Sun/8.11.6/TechFak/2003/04/16/pk) with ESMTP id hAKLJd104063;
	Thu, 20 Nov 2003 22:19:39 +0100 (MET)
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
Message-ID: <16317.12264.979185.14456@xayide.TechFak.Uni-Bielefeld.DE>
Date: Thu, 20 Nov 2003 21:44:00 -0000
To: Paul Eggert <eggert@CS.UCLA.EDU>
Cc: Ben Elliston <bje@wasabisystems.com>, gcc@gcc.gnu.org,
   binutils@sources.redhat.com, gdb@sources.redhat.com, rms@gnu.org
Subject: Re: flag day for Solaris portions of config.{guess,sub}
In-Reply-To: <87y8ua7nyl.fsf@penguin.cs.ucla.edu>
References: <8765hf4c8z.fsf@wasabisystems.com>
	<yddu14z3z8z.fsf@xayide.TechFak.Uni-Bielefeld.DE>
	<87k75u98bu.fsf@penguin.cs.ucla.edu>
	<16317.4758.255402.870324@xayide.TechFak.Uni-Bielefeld.DE>
	<87y8ua7nyl.fsf@penguin.cs.ucla.edu>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
X-SW-Source: 2003-11/txt/msg01130.txt.bz2

Paul Eggert writes:

> > I've just checked am-utils, ntp, and pidentd, and all of them are
> > affected.
> 
> No doubt other programs will be affected too.  But these programs are
> a relative handful.

This list came up from the first three that came to mind (and that I
contributed to at some point).  You create work for many maintainers for no
value to them whatsoever, only obscuring the configure scripts with
handling for solaris2.<x>, solaris<x> and some solaris<n> (or whatever)
when Sun comes up with a new name.

A continued burden which removes clarity from those scripts, in exchange
for a little less newby confusion (who will be confused by SunOS 5.x
vs. Solaris 2.x/x anyway).

	Rainer