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

[Mathieu Parent]

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>:
>> [...]
>>> 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).

Is upstream doing this? If not, what problem are e trying to solve?

>>> 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.

We don't have problem with PEAR because it doesn't use some specific
syntax for versions.

Using the composer parser won't help because it doesn't have AFAIK a
tool to convert to debian versioning (i.e

>
>> 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).

Regards
-- 
Mathieu