Mail Archives: djgpp/2015/09/05/17:38:49
On 09/05/2015 11:24 PM, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com] wrote:
> Am 29.08.2015 12:27, schrieb Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp 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
>>
>
>
> I have attached a script that will move the content of the /beta tree into a
> working directory called /current-2.05. Things from the /beta tree that I
> consider obsolete are moved into /deleted/beta. Archives from the /current
> tree that shall be retained are moved also into /current-2.05 directory.
> Archives that I consider obosolete are moved into /deleted. Before the whole
> procedure is started the script backups the complete /current directory for
> later restauration. When the procedure is finished the /beta directory will
> be empty, all obsolete archives from /beta und /current will have been moved
> into /deleted. The newly created directory tree /current-2.05 will contain
> all the archives that shall become part of the new DJGPP 2.05 release. The
> backup will recreate the full /current directory tree. This way both directory
> trees will coexist for a while. When it is decided that the /current-2.05 tree
> shall replace the old /current tree, that tree can simply be deleted. There is
> no need to care about files that should be moved form /current into /deleted
> because this has already be done by the script when populating the /current-2.05
> directory tree. When the whole procedure has been successfully finished, the
> original /current directory will be renamed to /current.old and the /current-2.05
> will be renamed into /current.
> The name /current.old is completely arbitrary and I would accept any other
> proposition.
>
> I will wait until tomorrow for some reaccion. If there are no _really serious_
> objections I will run the script tomorrow. I will also update mini-faq.txt to
> reflect for the new archives build with DJGPP-2.05.
Cloned my local mirror and run script on cloned version. Comments about results:
1) Files 00_index.txt should also be regenerated. One could use manifest/*.ver for text.
That can however be done separately. Maybe it's better to leave these files temporarily out
from new current directory and regenerate them after that
2) We do not need bsh204(s|b|d).zip in new current (that belongs to old one only)
3) I have not uploaded bsh205(s|b|d)r4.zip (it was only in my next/v2gnu directory).
I'll try to upload it in the morning
4) There is stale gdbm183b.zip and gdbm110br2.zip without source packages and
full set of gdbm111*br2.zip (gdb183b.zip gdbm110br2.zip should not be there)
5) there are 2 autoconf versions, but I guess it can stay so. Both are obsolete. Unfortunately there
is no newer ports
Additionally one one must be careful with source packages as for many packages there is no
source package in current beta.
Andris
PS. One more useful package is alpha/v2gnu/pkgc015s.zip and alpha/v2gnu/pkgc015b.zip.
I should perhaps rebuild it and put in current. It can however be done after switch. Newer pkg-config
version did not work even when I succeeded to build them as far as I remember (it was long time ago)
- Raw text -