[pkg-php-pear] Bug#714173: ITP: php-symfony-process -- Symfony PHP Framework - Process component

andrea rota a at xelera.eu
Sat Jun 29 00:30:17 UTC 2013

On Sat, Jun 29, 2013 at 02:35:15AM +0800, Thomas Goirand wrote:
> > other than this, i think php-symfony-process should be in rather good
> > shape by now:
> > http://anonscm.debian.org/gitweb/?p=pkg-php/php-symfony-process.git;a=summary
> I don't agree that it's in good shape. I think I have to insist here.
> Your package should:
> - depend on pear-symfony-channel (by the way, should it have been
> pear-symfony2-channel???)
> - depend on php-pear
> - contain a .reg for the PEAR package
> as for every other PEAR package...
> Currently, you fail to respect these essentials rules for a PEAR
> package, which means that the "process" Symfony package will appear as
> not installed when doing "pear list" for the symfony channel. Eg:
> For example:
> # pear config-set default_channel symfony2
> config-set succeeded
> # pear list
> Installed packages, channel pear.symfony.com:
> =============================================
> Package Version State
> Yaml    2.2.1   stable
> When I install your package, it should show here. It's not the case!
> Please use the upstream tarball from here and not Git:
> http://pear.symfony.com/get/Process-2.3.1.tgz
> so that you can use the package.xml from the tarball, and do a "normal"
> pear packaging. I don't even understand why something had to be done for
> phpcomposer. Maybe you can explain?
> and add the necessary ${phppear:Debian-Depends},
> ${phppear:Debian-Recommends} and ${phppear:Debian-Breaks} as I suggested.

these three php-symfony-* packages i'm working on are dependencies for
Composer, alongside two other PHP libraries which are only distributed
via composer itself (not via any PEAR channels), whereas the Symfony
components are distributed via both methods.

i started packaging these Symfony components with the dh_phpcomposer
helper as suggested previously on the pkg-php-pear list, but i see there
are different opinions.

i can re-package the Symfony components from pear.symfony.com if that is
the preferred method, of course.

can i depend on this even though it's not in sid yet?

pear-symfony-project-channel should be the obsolete one.


andrea rota

Xelera - IT infrastructures
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1530 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-php-pear/attachments/20130629/4ee3429b/attachment.sig>

More information about the pkg-php-pear mailing list