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

[David Prévot]

-----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>:
> [...]
>> Great. I have no idea how to handle multiple composer.json files with
>> dh_phpcomposer yet,
> 
> Why do you need this? This is not supported by composer itself.

You may have missed the beginning of this thread that is about building
the ~30 Symfony components as binary packages from the same source
package (that provides each component in a subdirectory).

>> and I wish we could use the Composer parser instead of
>> implementing our own in dh_phpcomposer, but those are two orthogonal
>> goals.
> 
> This will lead to a bootstrap problem, as composer is packaged using
> composer, with half-a-dozen dependencies.
> 
> And: what will this add? The json format is cleanly documented.

We maybe just made a poor job at implementing it, because it looks like
we piled up fixes and workarounds on the current parser for various
issues we came across recently. I would hope the Composer parser would
work well out of the box and avoid code duplication, allowing us to use
it as php-pear is used to parse parts or all of package.xml for PEAR
packages.

> Taking about it, I'm currently re-writing pkg-php-tools (almost) from
> scratch, with the following goals:

Sounds promising, thanks for your work!

Regards

David


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJTgexCAAoJEAWMHPlE9r082pYH/A9rTPLKN4a+RQkkpqTDOgX3
3sLlEhshIQH4uDVEm2pY+tRfc8+UA9e88j7DiKk3wsRTS1Y87/dgzHn2jJ1uTuYB
mUWk+wjwP37Fem5LW0cWUi8hcCJvxQLttBLkadO2xLIZ1x1iuxHYMTKSXUYQJ1sY
MB4f14aTBCfXDB4KAk0w8P4TE4ObPgtyXHJvXye2zTZKyOLziusMBWVxQzcIVRZd
dUEUqFq2f7IcHFnWewMMpFuuHYp/ADsVt3cfyn8Tv4yxkq6Uf564msZA43j/7MSG
KBDIg705wyimSMYMne58Ws3kajfA5WopItB5Iu/SbsOe1ok34JFX0sbf7TBBeAM=
=gxjh
-----END PGP SIGNATURE-----