Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60144
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.210.170 as permitted sender)
MIME-Version: 1.0
Sender: adam@adamharvey.name
In-Reply-To: <CAKOpQSzTqa6-hOGDGEZmwytEQwHN_2kGnXaObrinKGQ=fwBn2g@mail.gmail.com>
References: <CAKOpQSzTqa6-hOGDGEZmwytEQwHN_2kGnXaObrinKGQ=fwBn2g@mail.gmail.com>
Date: Wed, 18 Apr 2012 08:26:17 +0800
Message-ID: <CADajX4BKqS_zUc7wt=m5m2bPra8piKT_kiBCt_aw3Z8PCTcAiw@mail.gmail.com>
To: Kris Craig <kris.craig@gmail.com>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] PHP Dependencies
From: aharvey@php.net (Adam Harvey)

On 18 April 2012 06:40, Kris Craig <kris.craig@gmail.com> wrote:
> Forgive me if this has been addressed before, but I was wondering: =C2=A0=
Have we
> ever considered maintaining an RPM for PHP dependencies for each version
> branch? =C2=A0The are legitimate reasons why people prefer to build PHP m=
anually
> instead of building from a repo, but those reasons often don't extend to
> the various extensions. =C2=A0So ideally, it would be awesome to be able =
to
> build those from a repo and have them match the builds used by that
> particular PHP version. =C2=A0For example, on CentOS I might do something=
 like,
> "sudo yum install php-common --enablerepo=3DPHP5_3".

I'm not really sure there's much benefit to the PHP project itself
doing this =E2=80=94=C2=A0I know we still ship a spec file, but other than =
the
special case of Windows, I think it's better if we just ship a tarball
and let downstream maintainers work their magic from there, including
build dependency aids like this. It's hard to cover all the RPM-using
distributions with a single RPM, and it might be more hassle than it's
worth to try.

> I was actually thinking of creating and maintaining some RPM packages for
> that purpose, but I figured it might be good to find out if there's alrea=
dy
> a better method first.

You might want to talk to Remi Collet before putting much effort in;
he builds excellent RPMs for each version for Fedora, Red Hat and
CentOS and may well have some ideas on the best way to go about this.

Adam