[pkg-php-pear] Let's reconsider the way Symfony2 Components are packaged for Debian

Daniel Beyer dabe at deb.ymc.ch
Fri May 23 07:11:36 UTC 2014

On Thu, 2014-05-22 at 16:29 -0400, David Prévot wrote:
> [ Assuming everyone is on the list, I follow up there. ]
> Hi,
> Le 22/05/2014 13:14, Daniel Beyer a écrit :
> > 1. Upstream obsoleted distribution via PEAR
> […]
> > I took a quick look into each Symfony2 component
> > present so far in Debian and they all use dh_phppear.
> php-symfony-routing actually uses dh_phpcomposer, but I would move it to
> dh_phppear if I were to update it (because the current support of PEAR
> in Debian as a package helper is far superior to the Composer one),
> unless I wanted a version that is not distributed via PEAR anymore.

You're right with php-symfony-routing and I agree that dh_phppear is
just great for anything distributed via PEAR. But for Symfony2 this
seems to be no longer an option (Fabien sounded pretty definitive in his

> > 2. Multiple source packages for a project released at a whole
> > Symfony2 Components are released and maintained at a whole [4]. In my
> > opinion it should be the same in Debian: Have each component of Symfony2
> > in a binary deb and let those been build from a single source package.
> That would be nice, but it may need some update on dh_phpcomposer to
> handle multiple binary (and composer.json) packages. It may also need
> extra care: some package (build-)depends on some Symfony 2 components
> already, and one must check that a new version of a component doesn’t
> break existing packages and eventually coordinate a fix before uploading
> such a new version. The every-components-in-one-source approach makes
> the updating work more consequent.

Yes, dh_phpcomposer might needs some improvements and extra care is
needed. But I suspect we can deal with that. You sound like you're
generally agree with this approach, so I count you in. :-)

> How much (new and already packaged) components are we talking about here?

Two are missing as runtime dependencies and 14 more to run tests. I
attached a more detailed list to #748834 [1].

> Please note there have been former discussions about Symfony 2
> components this year on this list, starting with a PEAR vs. Composer one
> (but at that time, upstream was still distributing both).

Thanks for the info. I roughly browsed trough the mail archive and found
most discussing on this in June 2013. Given that PEAR no longer is an
option and dh_phpcomposer currently does not have an automatism to
package for Debian based on Composer as dh_phppear offered it for PEAR,
I vote for a classic Debian packaging for Symfony2 Components (use gbp
and debhelper, have a watch file in place, try to make use of
dh_phpcomposer as much as possible).


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748834#34
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-php-pear/attachments/20140523/965eeb8f/attachment.sig>

More information about the pkg-php-pear mailing list