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

"David Prévot" david at tilapin.org
Thu May 29 18:07:01 UTC 2014

Hi Daniel,

> On Mon, 2014-05-26 at 17:53 +0200, Mathieu Parent wrote:
>>> Le 25/05/2014 05:21, Mathieu Parent a écrit :

>> Is upstream doing this?

> Upstream maintains and releases Symfony at a [w]hole - see:
> https://github.com/symfony/symfony

> At the moment I'm manually
> adding the dependencies listed in each of those composer.json to
> d/control for each single binary package.

Ouch, that sounds needlessly painful and not sustainable: it will also
make updates and reviews an actual blocker, especially given the number of
components involved.

> Having some help from
> dh_phpcomposer here would be great.

I would consider it a must: if dh_phpcomposer can’t be tricked into
providing the needed dependencies (and the more I think about the way it
works, the more I wonder), I’m not sure packaging Symfony Components from
a unique source is actually worth it. Have you double checked the number
of new Symfony Components really needed for Silex?



More information about the pkg-php-pear mailing list