Mail Archives: djgpp/2015/08/29/11:00:00
On 08/29/2015 03:26 PM, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com] wrote:
> AmI 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
>
> The question arises how long should we collecting things that may be usefull for 2.05?
> A month more? a year more? five years more? And who decides what is worth to be collected or what needs to be ported to 2.05?
>
> We are working on/announcing the update to 2.05 since a quarter of a year and we have made no real progress. We are still collecting differnt updates of dj*.zip and other ports in /beta. If we wait until we considere that all "required" ports have been rebuild with DJGPP 2.05 then we will wait until the end of time. Who dicides what is required? Who decides what is nice to have? And who will volunteer to do this endless job?
> We should make a _definitive_ dead line to bring this to an end IMHO. And, if at all, we should define an absolute _minimal_ number of packages that still needs to be ported. Minimal means really required and certainly not nice to have. IMHO minimal means all those ports required to build djdev from sources. Everthing else is nice to have. Minimal certaily does not mean having a DJGPP 2.05 version of a port of wat3222br2.zip or tiff403b.zip or lua or whatever else someone may have on his wish list for x-mas. That are things that will be ported some day when someone (may be me) decides to sacrifice his spare time to do it.
I'm not asking to postpone it indefinitely.
Having new directory for 2.05 which is after that renamed to current as I suggested would allow us
to preserve current snapshot of v2.03 (old current) for reference if it would be ever needed.
Therefore I suggested copying required files from pub/djgpp/current, but moving from
pub/djgpp/beta. It would be similarly as there was copy of DJGPP v1 in current for rather long time
after v2 was already present.
We waited as there were critical packages not built recently enough,
I just think that it would be nice to take a look at the new directory before we switch. No need to
wait for month, year or more any more
Life would be much simpler if we would have decided to bump version to 3.0 as then we could have
v3, v2gnu, etc.
Andris
- Raw text -