Newsgroups: php.internals,php.webmaster
Path: news.php.net
Xref: news.php.net php.internals:72633 php.webmaster:18340
Return-Path: <petercowburn@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 76506 invoked from network); 15 Feb 2014 16:58:58 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 15 Feb 2014 16:58:58 -0000
Authentication-Results: pb1.pair.com header.from=petercowburn@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=petercowburn@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.45 as permitted sender)
X-PHP-List-Original-Sender: petercowburn@gmail.com
X-Host-Fingerprint: 209.85.216.45 mail-qa0-f45.google.com  
Received: from [209.85.216.45] ([209.85.216.45:55374] helo=mail-qa0-f45.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 22/05-45929-1DC9FF25 for <internals@lists.php.net>; Sat, 15 Feb 2014 11:58:58 -0500
Received: by mail-qa0-f45.google.com with SMTP id m5so6652307qaj.32
        for <multiple recipients>; Sat, 15 Feb 2014 08:58:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        bh=Lxf1RLx1sU0d3wjkPr13BaymYukBMue0R3A7h5gK3r8=;
        b=bXJk64n3LlDBtlu5JehZRqQU0OW4N+3b9jMeScYNlV8wzTcBUFRcY9nNFa/hLtliLv
         q1jlbY/ej9s2B5QPgV5JJXPxBmgefQnm2lYquUnnJ3Xpufi6bASvJWnSnKByJsGsQZs7
         bZeicuEHPzsJU/+rrEf2eSTrOjQ6I2qd7IaxxGGqoRJ1p5qUHumwDpze0c/dfRikz6Bx
         u2ru75KUM8QMlg4nxH6I/aKi7R0SfHUq3kJtTb38+o/XmxD2No8iyLiiLZ5uMFhrhh/6
         GmT5BMXMd/8j8M6oRD4w5Z1pDS+kilhq8m2dT9nKd9LpOxyTO2c8U2PeoFtpoWNC/Dsm
         X4eQ==
X-Received: by 10.140.97.73 with SMTP id l67mr21790764qge.56.1392483535628;
 Sat, 15 Feb 2014 08:58:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.96.165.103 with HTTP; Sat, 15 Feb 2014 08:58:15 -0800 (PST)
In-Reply-To: <CAH-PCH4fEriLzvG+8Pm7c1Mz=Wpw1gnDy2TruD=meETdLkrHow@mail.gmail.com>
References: <CAL2PKYdeRT=xtDJ3nPOC2c1NiOkvwfYR8aHVTxyJCTi50feSYA@mail.gmail.com>
 <CAH-PCH4fEriLzvG+8Pm7c1Mz=Wpw1gnDy2TruD=meETdLkrHow@mail.gmail.com>
Date: Sat, 15 Feb 2014 16:58:15 +0000
Message-ID: <CAPg3Xx+ZZywcdCooYQ96kmKN2Bmp8=K-E_T-j7UMu29Of8udHA@mail.gmail.com>
To: Ferenc Kovacs <tyra3l@gmail.com>
Cc: Rogerio Prado de Jesus <rogeriopradoj@gmail.com>, php-webmaster <php-webmaster@lists.php.net>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113a9cc47f69c404f274d6e1
Subject: Re: [PHP-DEV] Is there a rule in moving releases from distributions
 to museum?
From: petercowburn@gmail.com (Peter Cowburn)

--001a113a9cc47f69c404f274d6e1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 15 February 2014 16:12, Ferenc Kovacs <tyra3l@gmail.com> wrote:

> On Sat, Feb 15, 2014 at 4:35 PM, Rogerio Prado de Jesus <
> rogeriopradoj@gmail.com> wrote:
>
> > Hello,
> >
> > I'm involved with CHH/php-build project on GitHub, and one of the issue=
s
> is
> > getting more discussion:
> >
> >
> https://github.com/CHH/php-build/commit/226802e28591287c11b240943876d21b0=
3aec2f4#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 ther=
e.
> >
> > Thanks in advance!
> >
> > Rogerio
> > rogeriopradoj.com
> > about.me/rogeriopradoj
> >  =E1=90=A7
> >
>
> hi,
>
> We keep the release tarballs in the
> http://git.php.net/?p=3Dweb/php-distributions.git;a=3Dsummary git repo (w=
hich
> is in turn then git submoduled to the
> http://git.php.net/?p=3Dweb/php.git;a=3Dsummary git repo, which in turn w=
ill
> be
> provided as an rsync target, from where the php.net mirrors pull the file=
s
> 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.
>

We already do provide a basic API via the releases page. The response
includes whether the release is to be found on museum or not. For example,
all of PHP 5:

http://www.php.net/releases/index.php?serialize=3D1&version=3D5&max=3D1000


>
> ps: cc'ing the webmaster mailing list.
>
>
> --
> Ferenc Kov=C3=A1cs
> @Tyr43l - http://tyrael.hu
>

--001a113a9cc47f69c404f274d6e1--