Date: Wed, 19 Mar 2003 17:56:21 +0100
To: DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Re: Timetable for 2.04 releases
Message-ID: <20030319165621.GA6546@sprite.fr.eu.org>
Mail-Followup-To: DJGPP workers <djgpp-workers AT delorie DOT com>
References: <3E786C49 DOT 98016A87 AT phekda DOT freeserve DOT co DOT uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E786C49.98016A87@phekda.freeserve.co.uk>
User-Agent: Mutt/1.5.3i
From: Jeremie Koenig <sprite AT sprite DOT fr DOT eu DOT org>
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

Hello, DJGPP workers.

On Wed, Mar 19, 2003 at 01:10:33PM +0000, Richard Dawe wrote:
> Hello.
> 
> Here's a suggested timetable for 2.04 releases. OK, there aren't many
> times, so it's more of a table. Since the new DXE code sounds like a
> killer feature, let's do two alphas.

Well, while you're discussing about release things, there's a minor wish
I'd like to express. Althrough it is not necessary for typical usage, a
single tarball containing all the source, and only the source (just like
a full CVS checkout at the release date), would be useful in some cases.

For instance, in order to package a DJGPP cross-compiler for Debian, I
need to have the source, make a source package from it, which will
generate the actual binary packages. I can fetch a few zips and put
pieces together to get what I need, but it would be more clean to get it
directly from some DJGPP mirror (maybe even gpg/pgp signed ?).

If I just missed the file, sorry.

And while i'm posting, include/getpagesize.h and include/sys/sysmacros.h
have execution mode bits set while fetched from CVS. No great issue,
just to let you know.

-- 
Jeremie Koenig <sprite AT sprite DOT fr DOT eu DOT org>