On Sat, Feb 15, 2014 at 4:35 PM, Rogerio Prado de Jesus < rogeriopra...@gmail.com> wrote:
> Hello, > > I'm involved with CHH/php-build project on GitHub, and one of the issues is > getting more discussion: > > https://github.com/CHH/php-build/commit/226802e28591287c11b240943876d21b03aec2f4#commitcomment-5230260and > https://github.com/CHH/php-build/pull/175. > > What I'd like to know is if there is a rule in moving releases from > distributions to museum? > > This way we could in php-build plan better how to solve the issues there. > > Thanks in advance! > > Rogerio > rogeriopradoj.com > about.me/rogeriopradoj > ᐧ > hi, We keep the release tarballs in the http://git.php.net/?p=web/php-distributions.git;a=summary git repo (which is in turn then git submoduled to the http://git.php.net/?p=web/php.git;a=summary git repo, which in turn will be provided as an rsync target, from where the php.net mirrors pull the files required for them to work. We move the old packages from the distributions repo to the museum to shrink the size of the checkout and the space requirement for the mirrors. I'm fairly sure that we won't be able to change that and provide each and every archive tarball from http://museum.php.net/ on our php.net mirrors. What we could do is maybe setting up an api to fetch the download url(s) for a given release or to set up a redirect pointing to museum if the requested archive seems to be sane, but it isn't found on the mirror. Let's see what others think. ps: cc'ing the webmaster mailing list. -- Ferenc Kovács @Tyr43l - http://tyrael.hu
