[pkg-php-pear] Common Symfony meta package (was: Symfony package review)

Daniel Beyer dabe at deb.ymc.ch
Tue Sep 23 18:26:13 UTC 2014

[Splitting this to it's own thread]

Hi David,

I just wanted to give you my current opinion on this. Please take your
time to think trough it and don't get abstracted from other, more
important work you (I'm pretty sure) have. The matter of having a common
symfony meta package in my opinion is not urgent anyway (and probably
even better dealt with at a later time).

Please find my reply inline...

> Am Sonntag, den 21.09.2014, 18:09 -0400 schrieb David Prévot:
> > Le 21/09/2014 14:14, Daniel Beyer a écrit :
> >> On Mon, 2014-09-08 at 10:04 -0400, David Prévot wrote:

> >> - I kinda liked the idea of a meta symfony package, what changed your
> >>   mind about it? (Thinking about doctrine and zendframework, I think it
> >>   will be nice to keep those (empty) packages once split too, but maybe
> >>   am I seeing it wrong);
> > 
> > I think php-symfony-framework-bundle does serve this purpose already.
> > But I'm open to re-add such a meta package again. But we maybe at least
> > do not depend on php-symfony-locale in it, since it is deprecated
> > starting with 2.3.
> > I'm not adding such a meta package back again for now, but if you still
> > think it should, fell free to open up a new thread.
> To be continued (will have to make up my mind about it), but a binary
> package with a name as simple as symfony may be easier to find than
> php-symfony-framework-bundle if people are willing to install it.

I agree that php-symfony-framework-bundle can easily overlooked to be
the "common" Symfony package. But "people are willing to install it"
made me think about it from an other perspective:

Such a package clearly would be made for Debian users in my opinion.
But compared to the composer world, the whole Debianized Symfony stack
is not really working out of the box, since we (currently) have no real
substitute in Debian for composer's autoloading capabilities.

Think about the following example:
use Symfony\Component\Finder\Finder;
$finder = new Finder();

Composer allows me to do such stuff without caring much about
autoloading. Therefor as a Debian user I would expect this to work after
having php-symfony-all (just a stub name) installed, as well. Instead I
would be disappointed, since I only get a PHP fatal error.

We partly could substitute this with README.Debian files and point
complaints of users (e.g. via bugreports) to those.
Alternatively we could develop a custom solution just made for a
php-symfony-all package.
But I would prefer to see a more general approach in Debian.

My (personal) conclusion:
Better not provide a packages that looks like it provides the Symfony
stack as long as it is not easy to use.

-------------- 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/20140923/af6cba0c/attachment.sig>

More information about the pkg-php-pear mailing list