X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10112150424.AA14812@clio.rice.edu>
Subject: Re: Refresh Proposal
To: acottrel AT ihug DOT com DOT au (Andrew Cottrell)
Date: Fri, 14 Dec 2001 22:24:26 -0600 (CST)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <005701c184f8$3607a0f0$0102a8c0@acceleron> from "Andrew Cottrell" at Dec 15, 2001 10:36:22 AM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

> > I'm sure there are some other suggestions
> Only one addition that I can think of that may make a difference if people
> want to re-build thinks, that is :-
>     Bash 2.04

This one intimidated me (2.04 vs 2.05, package replacements for libc, etc)
vs a straight compile.  I'd need advice.

> > It turns out I have binaries to repackage all of the above done except
> > bnu2112b.  With the above list done the goal would be to make Win2K/XP
> > self hosting again via simtel - if something is broken then the user
> > could fix it himself with a recompile/build of a package.
> 100% agree, but they propbably won't re-build the packages, instead they
> will compain that package X doesn't work on 2K or XP. If this occurs then it
> may be worth updateding these packages as and when required.

Today people have a good excuse for not trying to rebuild.  Admittedly
some people might complain, but others will refresh a build as part of
the project if they see problems.  I'm not saying they don't get replaced,
I'm just saying that *I* don't do it on the first pass :-)

Today, if a package doesn't do certain things (like spawning, renaming to
existing files, special handle ops, etc) the 2.03 images work fine on W2K/XP.