Request for version bump Symfony 2.0 is released today. Reproducible: Always
I do not see this as a version bump really. Not even a new slot. Symfony 2 is fundamentaly different from Symfony 1 and porting is non-trivial. I'll add a new package when I see new ebuilds :)
it's a good idea to create a new package for it. as attachment my first attempt. what do you think? maybe it's better to install as webapp?
Created attachment 281555 [details] symfony2-2.0.0.ebuild
I have not looked much into symfony 2 yet. If the recommended way of using symfony 2 is to bundle it with the project, then we should not provide it as a package at all. If it is okay that it lives in /usr/share/php, then it is okay. Installing it as a webapp does not make much sense to me since either it is installed as a "shared library" or it is bundled with the actual application. Regarding the ebuild, you should use php-pear-lib-r1 eclass, I believe. Also, should it not install an executable? If we want this package in the tree, I think it makes the most sense to provide the version without vendors and it should be installed from http://pear.symfony.com/, each component alone :) This one may help you create the ebuilds, but need to be hacked a little to support channels etc. Also, you should probably create an ebuild that installs (discovers) the channel. I have been meaning to do that, but not had the time yet. https://github.com/olemarkus/epear
Created attachment 284981 [details] dev-php.tgz: archive with ebuilds for dev-php
I've used the epear tool. looks great. In attchment there are the changed symfony2 and related pear packages as standalone packages.
I think we need a prefix for all these components. Names like "Form" and "Process" are far too generic and stops other frameworks from having the same approach if we go down this route. I also think we should hold off on a "symfony2" ebuild until we can add any value, such as a way to bootstrap a new project with that version. Because of how symfony does the "distributions" (ie. a skeleton app), /usr/share/php does not seem like the right place for this as you'd basically start a project with: cp -r /usr/share/php/Symfony/Symfony ./ Which isn't really ideal? Not sure of a more elegant way at the moment.
I'm currently maintaining all the Symfony2 Components in an overlay[1] whilst it's debated whether to include them in the tree. Any suggestions on some value that Gentoo can add apart from having them readily available on the system "the Gentoo way" are welcome. [1] https://github.com/jamiel/gentoo-overlay
I've stopped supported these ebuilds in my overlay in favour of composer. If you think it's a good idea to have composer in the tree voice your opinion in bug 439206 . I think we can close this bug as no-one is going to maintain Symfony2 directly in the tree and it doesn't make much sense anymore.
Closing - please re-open if there is a strong argument to have this in the tree.
*** Bug 473570 has been marked as a duplicate of this bug. ***
