delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1996/11/03/04:10:37

Date: Sun, 3 Nov 1996 11:07:23 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT edu DOT ar>
Cc: DJGPP-WORKERS AT delorie DOT com
Subject: Re: DJ: can you put the new files separated?
In-Reply-To: <9611011735.aa02559@ailin.inti.edu.ar>
Message-Id: <Pine.SUN.3.91.961103105754.27986E-100000@is>
Mime-Version: 1.0

On Fri, 1 Nov 1996, Salvador Eduardo Tropea (SET) wrote:

> Can you put the corrected files of the package in separated files with the 
> package structure?
> In this way is much more easy to download just the patched part of the 
> package.

If you are talking about the library patches, just subscribe to
djgpp-workers and install every posted patch which you believe is
important into your private copy of the library.  That's what I've been 
doing for ages.

Anyway, this raises the important (IMHO) issue of DJGPP updates between 
major releases, and I'll just grab this opportunity to suggest something 
I've been thinking for a long time.  It might be a good idea to have a 
directory where users could find patched exe binaries and either a 
patched .a libraries or (better still) compiled .o files ready to be put 
into a library.  The source-level patches should be also available there, 
as the least docs of the patch and its reason.  I even thought about an 
automated way that will take patches submitted to the bug-tracking system 
and produce such patched files automatically, but that might be too 
far-fetched (and many bugs don't get submitted there anyway).

An alternative would be to update the affected zips much more frequently 
(like every month or so), but that would probably be too much of a burden 
for DJ and for the people who would like to download the fixed zips.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019