dev-php/ZendFramework bump please - new major version ( 2.0. 6 ) available
Just as with Symfony2, we feel that Zend Framework is best installed out-of-tree through composer or similar, and that having a system-wide installation does not make much sense.
Ole, does it also apply to ZendFramework-1.12.3? If not I'd like to ask you to add new ebuild for version 1.12.3 of ZendFramework.
*** Bug 505130 has been marked as a duplicate of this bug. ***
(In reply to Ole Markus With from comment #1) > Just as with Symfony2, we feel that Zend Framework is best installed > out-of-tree through composer or similar, and that having a system-wide > installation does not make much sense. Why do you feel like that? Try to think and you maybe figure it out that system wide installer of this library is much better. I will give you an example: "Few years ago when I had training in ZF 1 we had to install ZF on ours computers. I just typed emerge ZendFramework and everything was working because I had Gentoo but my friends who had Ubuntu had to download it manually and copy it to some location on theirs disks. And they failed to do it, they didn't have proper dependencies installed. They had to install them manually one by one. They had a lot of work and I was just sitting there smiling." Now you maybe "feel" why there should be ebuild for ZendFramework.
(In reply to Bartosz Krzeszewski from comment #4) > (In reply to Ole Markus With from comment #1) > > Just as with Symfony2, we feel that Zend Framework is best installed > > out-of-tree through composer or similar, and that having a system-wide > > installation does not make much sense. > > Why do you feel like that? Try to think and you maybe figure it out that > system wide installer of this library is much better. I will give you an > example: "Few years ago when I had training in ZF 1 we had to install ZF on > ours computers. I just typed emerge ZendFramework and everything was working > because I had Gentoo but my friends who had Ubuntu had to download it > manually and copy it to some location on theirs disks. And they failed to do > it, they didn't have proper dependencies installed. They had to install them > manually one by one. They had a lot of work and I was just sitting there > smiling." Now you maybe "feel" why there should be ebuild for ZendFramework. The dependencies are managed through composer so this is not an issue. Most projects would rather bundle these libraries anyway because sometimes these libraries make incompatible changes. As a result, when the system library is upgraded, it will break your code. This way the developer has more control of what dependencies and versions of dependencies the software needs and can upgrade it when he has a chance to migrate the code as opposed to a system upgrade forcing him into it.
(In reply to Matthew Schultz from comment #5) > (In reply to Bartosz Krzeszewski from comment #4) > > (In reply to Ole Markus With from comment #1) > > > Just as with Symfony2, we feel that Zend Framework is best installed > > > out-of-tree through composer or similar, and that having a system-wide > > > installation does not make much sense. > > > > Why do you feel like that? Try to think and you maybe figure it out that > > system wide installer of this library is much better. I will give you an > > example: "Few years ago when I had training in ZF 1 we had to install ZF on > > ours computers. I just typed emerge ZendFramework and everything was working > > because I had Gentoo but my friends who had Ubuntu had to download it > > manually and copy it to some location on theirs disks. And they failed to do > > it, they didn't have proper dependencies installed. They had to install them > > manually one by one. They had a lot of work and I was just sitting there > > smiling." Now you maybe "feel" why there should be ebuild for ZendFramework. > > The dependencies are managed through composer so this is not an issue. Most > projects would rather bundle these libraries anyway because sometimes these > libraries make incompatible changes. As a result, when the system library > is upgraded, it will break your code. This way the developer has more > control of what dependencies and versions of dependencies the software needs > and can upgrade it when he has a chance to migrate the code as opposed to a > system upgrade forcing him into it. 1. "As a result, when the system library is upgraded, it will break your code. This way the developer has more control of what dependencies and versions of dependencies the software needs and can upgrade it when he has a chance to migrate the code as opposed to a system upgrade forcing him into it." So in short you say that we don't use package.mask and package.use anymore? So why use Gentoo? 2. "Starting with Zend Framework 2, you may now install Zend Framework or any of its individual components and their dependencies, using the dependency management tool Composer." Composer is ZF 2 feature, in bug: 505130 I requested new version of ebuild for ZF 1 which dosen't have this tool. 3. ZF 1 is in portage (be consistent and remove it). 4. When I speak about dependencies I think about php, apache and various use flags. 5. I use ZF 1 on my development computer and I have a lot of projects on it. Having system wide ZF 1 library saves a lot of disk space and copy time. 6. I use ZF 1 for a few years and there haven't been even one situation when upgrade broke things. I upgraded it recently to the latest version and everything just works. 7. I really think that bug: 505130 should not be a duplicate of this bug. ZF 1 and ZF 2 are two different libraries.
+*ZendFramework-1.12.9 (07 Oct 2014) + + 07 Oct 2014; <grknight@gentoo.org> +ZendFramework-1.12.9.ebuild, + -ZendFramework-1.11.6.ebuild: + Version bump for wrt bug 448576 and security bugs 451060, 505276 and 523198 ZF2 will remain uncommitted as it is meant to be done via composer
