[pkg-php-pear] Are you planing to release a Symfony 2.7.9+dfsg-2? (Was: Re: Symfony 2.8)

David Prévot david at tilapin.org
Tue Feb 16 15:28:56 UTC 2016

Hi Daniel,

Le 16/02/2016 10:39, Daniel Beyer a écrit :
> Am Dienstag, den 16.02.2016, 08:57 -0400 schrieb David Prévot:

>> […] we could push
>> php-symfony-security-{core,csrf,http,*} in the archive and have
>> php-symfony-security depending on them. We might even push a big
>> (php-)symfony package depending on all binary packages (using the main
>> composeer.json file).
> Actually splitting php-symfony-security-* into separate packages came
> into my mind today, too. I once was against doing this, but can't
> remember the reason for it - and as of today I think splitting
> php-symfony-security-{core,csrf,guard,http} would be the better
> approach.

OK, you already cherry-picked most of the tiny changes needed to make
that happen. I still have to figure out what is left to hack to make
php-symfony-security a proper package ;).

> Regarding a php-symfony package, I personally think it is not of much
> use. But I guess it does not harm either, so I'm okay with such a one.

Any preference about the name? “symfony” as it might be expected by
someone who wants “all the stuff” to work with it, or “php-symfony” to
follow the Composer naming scheme (but as php-symfony-polyfill, packages
depending on it are unlikely, or are probably doing it wrong anyway)?

>> I’d be happy to work on that if you agree.
> And I would be happy if you could work on it. ;-)

OK, I’ll take care of that. It should be independent enough from what
you’re working on to make it easy to merge/rebase when it’s ready.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-php-pear/attachments/20160216/f3c8aed3/attachment.sig>

More information about the pkg-php-pear mailing list