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

Daniel Beyer daniel.beyer at ymc.ch
Thu May 29 18:15:19 UTC 2014

On Sat, 2014-05-24 at 15:33 +0200, Daniel Beyer wrote:
> On Fri, 2014-05-23 at 17:12 -0400, "David Prévot" wrote:
> > Hi Daniel,
> > 
> > (..)
> > You may wish to transform #513646 as your ITP too.
> > 
> Just done that. I'll put a repo on git.d.o/git/pkg-php as soon as I have
> something worth putting there.

I've pushed some initial packaging, which can be found at:

David, you might want to take a look onto this and check if I'm on the
right track.

I decided that manually adding all those dependencies to d/control is
much too error-prone and found a hackish way to use dh_phpcomposer for
that: I simply temporarily symlink the /debian folder on each
component's source-dir and run dh_phpcomposer from there).
Having a way to tell dh_phpcomposer where to look for composer.json
would be great, but I did not found the to check how this could be
implemented, yet.

I'll add the rest of the 28 components soon and do a license check.

I'm not sure which version of Symfony to package. According to
upstream's roadmap [1]:
- 2.3 series is an LTS and gets security fixes till 05/2017
- 2.4 series gets those till 01/2015
- upcoming 2.5 till 07/2015
- 2.6 most likely will not be released in time for the Jessie freeze

In order to benefit the most from upstream's maintenance work, I tend to
go back to 2.3 (for Jessie). What's your opinion on that?

BTW: I checked the currently packaged components in Debian. Only
php-symfony2-yaml has a version newer than 2.3. 

[1] http://symfony.com/roadmap

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-php-pear/attachments/20140529/5b5334b8/attachment.sig>

More information about the pkg-php-pear mailing list