X-Authentication-Warning:	kendall.sfbr.org: jeffw set sender to jeffw AT darwin DOT sfbr DOT org using -f
Date:	Wed, 21 Mar 2001 13:22:51 -0600
From:	JT Williams <jeffw AT darwin DOT sfbr DOT org>
To:	djgpp-workers AT delorie DOT com
Subject:	Re: About release of gcc-2.95.3 for DJGPP
Message-ID:	<20010321132251.E3532@kendall.sfbr.org>
Mail-Followup-To:	djgpp-workers AT delorie DOT com
References:	<CAEGKOHJKAAFPKOCLHDIOEMKCBAA DOT tim DOT van DOT holder AT pandora DOT be> <Pine DOT A41 DOT 4 DOT 05 DOT 10103212005120 DOT 135218-100000 AT ieva06 DOT lanet DOT lv>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<Pine.A41.4.05.10103212005120.135218-100000@ieva06.lanet.lv>; from pavenis@lanet.lv on Wed, Mar 21, 2001 at 08:24:51PM +0200
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

-: Unfortunatelly as we know from earlier experience, many users don't read 
-: readme files, so perhaps somebody will simply try to use binaries of
-: gcc-2.95.3 together with old binutils and run into trouble. It's mentioned
-: in gnu/gcc-2.953/problems.txt but the question is, how many users will see
-: it. But I don't see any other reasonable way how to force users to upgrade
-: binutils (we cannot provide compatibility with old binutils forever ...) 

Wasn't someone working on a DJGPP system checking utility (not zippo),
that would try to ferret out things like this?  The initial approach might
be a simple script that checks the manifest/ directory for incompatible
package versions; something makefile- or autoconf-ish might be better in
the long run.  Assuming, of course, that the user hasn't nuked manifests/
or otherwise molested the expected djgpp tree (yeah, right).

- Raw text -