X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
Date: Tue, 7 Dec 2004 11:54:34 -0500
Message-Id: <200412071654.iB7GsYYg002730@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <200412071852.42299.pavenis@latnet.lv> (message from Andris
	Pavenis on Tue, 7 Dec 2004 18:52:42 +0200)
Subject: Re: Patches to build GDB 6.3
References: <01c4c987$Blat.v2.2.2$52b9e920 AT zahav DOT net DOT il> <200412071838 DOT 09466 DOT pavenis AT latnet DOT lv> <200412071638 DOT iB7GcUjp002093 AT envy DOT delorie DOT com> <200412071852 DOT 42299 DOT pavenis AT latnet DOT lv>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> If we change things only beginning with GCC-4.0, then new GDB versions will be 
> unusable with for example gcc-3.4.3.

I think we should worry about that, but I'm trying to think of a way
to make it easy for DJGPP users to know that they have a consistent
set of stuff.  We have a couple of big new releases coming up, it's an
opportunity to make it easy to sync up stuff.  Expecting most users to
keep track of a myriad of versions is a bad idea, although some users
will prefer that over upgrading lots of packages.