Zend Framework 2 was managed in a single git repository and distributed as a big archive. php-ZendFramework2 is packaged from this archive (1 sub package per component)
With 2.5, the framework is now split into 1 git repo per component, each having its own life cycle.
I think it make sense to follow upstream on this, as it is more simple to maintain "some" small packages instead of a big one (even if this imply a bootstrap for initial build)
All the packages are ready, see https://github.com/remicollet/remirepo/tree/master/php/zend
php-zendframework-zendpdf have just been approved, see https://bugzilla.redhat.com/1251034 (as this one is new, not part of ZF 2.4)
All the spec are copy/paste from a template one (mostly, only description and dependencies are specific)
All use the same License (BSD), as split off the big project.
Plan for Fedora 24 (and perhaps Fedora 23 later)
I think this is a good candidate for Mass review exception.
I agree that this is a good candidate for a mass review exception. Are these packages intended for EL5? If not, I would really suggest cleaning the EL5-specific cruft out of the spec.
Replying to [comment:2 tibbs]:
Are these packages intended for EL5? If not, I would really suggest cleaning the EL5-specific cruft out of the spec.
Fedora only (requires PHP > 5.5). EL-5 stuff is usually not a blocker for review, and I need them for my repository, but I'm used to clean them during the import in fedora git.
We discussed this at this weeks meeting (http://meetbot.fedoraproject.org/fedora-meeting-1/2015-09-24/fpc.2015-09-24-16.00.txt):
Bug tracker https://bugzilla.redhat.com/1266336
I've created all of the packages.
Note that this means we currently php-ZendFramework and php-zendframework in the distro, which could be quite fun.
Metadata Update from @tibbs: - Issue assigned to james
Login to comment on this ticket.