[pkg-php-pear] Let's reconsider the way Symfony2 Components are packaged for Debian
taffit at debian.org
Thu May 22 20:29:44 UTC 2014
-----BEGIN PGP SIGNED MESSAGE-----
[ Assuming everyone is on the list, I follow up there. ]
Le 22/05/2014 13:14, Daniel Beyer a écrit :
> 1. Upstream obsoleted distribution via PEAR
> I took a quick look into each Symfony2 component
> present so far in Debian and they all use dh_phppear.
php-symfony-routing actually uses dh_phpcomposer, but I would move it to
dh_phppear if I were to update it (because the current support of PEAR
in Debian as a package helper is far superior to the Composer one),
unless I wanted a version that is not distributed via PEAR anymore.
> 2. Multiple source packages for a project released at a whole
> Symfony2 Components are released and maintained at a whole . In my
> opinion it should be the same in Debian: Have each component of Symfony2
> in a binary deb and let those been build from a single source package.
That would be nice, but it may need some update on dh_phpcomposer to
handle multiple binary (and composer.json) packages. It may also need
extra care: some package (build-)depends on some Symfony 2 components
already, and one must check that a new version of a component doesn’t
break existing packages and eventually coordinate a fix before uploading
such a new version. The every-components-in-one-source approach makes
the updating work more consequent.
How much (new and already packaged) components are we talking about here?
Please note there have been former discussions about Symfony 2
components this year on this list, starting with a PEAR vs. Composer one
(but at that time, upstream was still distributing both).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----END PGP SIGNATURE-----
More information about the pkg-php-pear