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

Daniel Beyer dabe at deb.ymc.ch
Thu May 29 19:30:26 UTC 2014

On Thu, 2014-05-29 at 14:07 -0400, "David Prévot" wrote:
> Hi Daniel,
> (..)
> > 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?

Yeah, I figured out doing that manually is not a good idea at all. As I
just wrote [1] I managed to let dh_phpcomposer do that for me. Now it's
only about adding some nice descriptions to d/control (and decide which
version to package and do a license check and probably drop the
depend-on-all-components metapackage I put in d/control at the very
beginning, since I doubt it makes sense).


-------------- 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/20140529/e037d4b7/attachment.sig>

More information about the pkg-php-pear mailing list