Everything

php

old PHP releases on mirror sites

php.internals

Gabor Hojtsy

21 years ago

Hi,

Could some guys look into the downloads available from php.net:

http://cvs.php.net/phpweb/distributions/

There are quite a few 2 and even 3 years old patchfiles, like:

rfc1867.c.diff-4.0.6.gz
php-4.3.0-to-4.3.1.patch.gz
php-4.0.6-to-4.1.1.patch.gz
php-4.0.6-memlimit.diff.gz
fd_patch-php-4.3.2.diff.gz
....

I would remove them, but it would be nice if someone would strengthen me
in this, so that my head will not get shouted off if I remove some
important stuff.

Also I would remove quite a few dated packages, since most of them are
available through the PHP museum, but then again, not all of them. The
museum has:

php-4.3.1-installer.exe
php-4.3.2-installer.exe
php-4.3.4-installer.exe

But no 4.3.3 installer. Also the museum seems to have been updated last
time around 4.3.9RC1, so it might need some new stuff added.

Removing stuff means less load on the CVS server for people checking out
phpweb and less load on the rsync server for people setting up private
mirrors.

Goba

Ilia A.

21 years ago

As long as we retain copies of those releases somewhere (php museum) I
see no reason to keep releases older then 3 versions in the
distributions folder.

Ilia

Gabor Hojtsy

21 years ago

> As long as we retain copies of those releases somewhere (php museum) I
> see no reason to keep releases older then 3 versions in the
> distributions folder.

Good. Those big patches are not available from the museum though.

Goba

Andi Gutmans

21 years ago

At 09:43 PM 12/15/2004 +0000, Gabor Hojtsy wrote:

>>As long as we retain copies of those releases somewhere (php museum) I
>>see no reason to keep releases older then 3 versions in the distributions
>>folder.
>
>Good. Those big patches are not available from the museum though.

I don't even think we need to keep more than the current and *possibly* one
version back. All the rest can head for the museum as we don't make them
accessible via php.net anyway.

Andi