# PHP Dependencies

- Thread: https://externals.io/message/60120
- Original archive: https://news-web.php.net/php.internals/60120
- Started by Kris Craig on 2012-04-17T22:40:09+00:00
- Messages: 2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #60120 — Kris Craig — 2012-04-17T22:40:09+00:00

URL: https://externals.io/message/60120#60120

Hey guys,

Forgive me if this has been addressed before, but I was wondering:  Have we
ever considered maintaining an RPM for PHP dependencies for each version
branch?  The are legitimate reasons why people prefer to build PHP manually
instead of building from a repo, but those reasons often don't extend to
the various extensions.  So 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.  For example, on CentOS I might do something like,
"sudo yum install php-common --enablerepo=PHP5_3".


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 already
a better method first.

Thanks!

--Kris

---

## #60144 — Adam Harvey — 2012-04-18T00:26:17+00:00

URL: https://externals.io/message/60120#60144 · In reply to: #60120

> Forgive me if this has been addressed before, but I was wondering:  Have we
> ever considered maintaining an RPM for PHP dependencies for each version
> branch?  The are legitimate reasons why people prefer to build PHP manually
> instead of building from a repo, but those reasons often don't extend to
> the various extensions.  So 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.  For example, on CentOS I might do something like,
> "sudo yum install php-common --enablerepo=PHP5_3".

I'm not really sure there's much benefit to the PHP project itself
doing this — I 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 already
> 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