Newsgroups: php.internals,php.mirrors
Path: news.php.net
Xref: news.php.net php.internals:852 php.mirrors:16697
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Fri, 11 Apr 2003 17:29:22 +0200
In-reply-to: <3E96DC2A.2020801@easydns.com>
To: colin@easydns.com
Cc: webmaster@php.net, internals@lists.php.net
Message-ID: <200304111729.22199.gabor@hojtsy.hu>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Content-disposition: inline
User-Agent: KMail/1.5
References: <200304111652.10504.gabor@hojtsy.hu> <3E96DC2A.2020801@easydns.com>
Subject: Re: too much distributions on php.net
From: gabor@hojtsy.hu (Gabor Hojtsy)

> I could not agree more!  Let's clean up that distributions directory and
> maybe only keep the latest two 4.x releases and the latest one 3.x
> release.  So, in this case that would be:
>
> 	php-4.3.1
> 	php-4.3.0
> 	php-3.0.18
>
> Also, do we need both .gz and .bz2 versions releases?  I think we could
> decide on one.

Well, the bz2 version for the latest PHP is approx. 1MB smaller then the gz 
version. I guess developers who download PHP source have bz2 on their 
machines. Or is there any linux/unix without bz2 support? Or do we assume 
that guys on Windows are unable to unbzip2 the download [also noting that the 
docs are only provided in bz2 now!].

> As for what to do with the older stuff ... I know someone had started a
> PHP museum with all the older releases back to PHP 1.x I think.
> Hopefully bandwidth isn't an issue for that person, but if it is, is
> there any reason we couldn't start a sourceforge project called "PHP
> Museum" or something, and store all the old releases and patches there?
>  I'm willing to maintain it.

It was Mark AFAIK, and I don't think he has bandwidth problems. There is 
probably not too much traffic there. The site is also linked from the 
downloads page.

Goba