X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
Subject:	Re: ANNOUNCE: DJGPP 2.05 release candidate
To:	djgpp AT delorie DOT com
References:	<201506091634 DOT t59GY0Bk000493 AT delorie DOT com>
	<55E17D7D DOT 4030406 AT gmx DOT de>
From:	"Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Message-ID:	<55E1891C.1070303@iki.fi>
Date:	Sat, 29 Aug 2015 13:27:40 +0300
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
	Thunderbird/38.1.0
MIME-Version:	1.0
In-Reply-To:	<55E17D7D.4030406@gmx.de>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 08/29/2015 12:38 PM, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com] wrote:
>
> During this week-end I will update the complete DJGPP distribution to DJGPP 2.05.
> This includes the rebuilding of all dj*zip archives so the lates changes of the
> v2_05_1 branch is in the library and the moving of all new archives from the /beta
> tree into the /current tree.  Obsolete archives from the /current tree will be moved
> into the /deleted tree.  Obsolete archives from the /beta tree will be moved into
> the /deleted/beta tree.  Nothing will be lost.
>
> I will keep the latest version of every compiler serie.  A compiler serie is defined
> by its last version digit.  E.g. if there are gcc200, gcc201, gcc202, gcc205 then I
> retain gcc205 and all the other ones will be moved into /deleted. Attention: gcc20X
> is a different serie than gcc21X.  This has the consecuence that a lot of compiler
> versions will remain in the /current directory.  If this is not wanted this is the
> last occasion to speak.
>
> To fullfill this task I will use a slightly modified version of the script proposed in:
> http://www.delorie.com/archives/browse.cgi?p=djgpp/2015/08/16/08:08:18
> I have got neither a positive nor a negative reponse to that proposision so I will assume
> that all agree and I will go ahead.
>
> I still have to do some preparations for all this, and that will take the rest of the day.
> During this day I will wait for objections or suggestions and tomorrow I will update the
> /current directory if there are no ____really serious____ objections.

I would still prefer collecting required stuff for v2.05 in a new directory:
- needed files from beta gets MOVED to this directory
- files from current gets COPIED

After that we can move current away and rename new directory as current. As the result we
have complete old current somewhere else and new version replaces it as /ftp/djgpp/current.

I think that way is safer and one can have some short time (like a week) to see whether
something more needs to be updated (of course replacement could be done also immediately after
files are collected in the new directory)

About GCC versions:
- 3.4.6, 4.7.4, 4.8.5, 4.9.3 and 5.2.0 should be in new current directory (that includes also 
gpc-3.4.6)
All gcc builds older than from this year can go to ftp/deleted/...

GMP, MPFR and MPC - perhaps only newest version should be kept

I should also sometimes build binutils-2.25 RPMs for /pub/ftp/rpms

Andris

- Raw text -