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

Daniel Beyer dabe at deb.ymc.ch
Mon May 26 17:01:26 UTC 2014


On Mon, 2014-05-26 at 17:53 +0200, Mathieu Parent wrote:
2014-05-25 15:12 GMT+02:00 David Prévot <david at tilapin.org>:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > Hi,
> >
> > Le 25/05/2014 05:21, Mathieu Parent a écrit :
> >> 2014-05-24 16:13 GMT+02:00 "David Prévot" <david at tilapin.org>:
> (...)
> 
> Is upstream doing this? If not, what problem are e trying to solve?
> 

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

Additionally so called subtree splits are provided for each component,
but packaging each single one based on that on its own is not the way we
should maintain them in Debian. Besides that those subtree splits mainly
exists for Composer (as far as I know) and some kind of automatism
updates them magically.


> (...)
> 
> >
> >> Taking about it, I'm currently re-writing pkg-php-tools (almost) from
> >> scratch, with the following goals:
> >
> > Sounds promising, thanks for your work!
> 
> Yes. I hope to fulfill milestone 1 before mid-july (yes I'm very busy).
> 

It really sound's promising. From my current perspective especially
milestone 2 (the composer related things). At the moment I'm manually
adding the dependencies listed in each of those composer.json to
d/control for each single binary package. Having some help from
dh_phpcomposer here would be great.


Greetings
Daniel

-------------- 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/20140526/4a8d24ca/attachment.sig>


More information about the pkg-php-pear mailing list