Well, we have a PEAR channel for distributing ZF as a singular package.
http://pear.zfcampus.org
From what I know, we are still undecided and do not plan on addressing
distribution of components on an individual basis.
From a maintenance standpoint, we would not be able to maintain
multiple components as their own project. Furthermore, from a support
standpoint, it even harder to ensure that version mismatches (between
coupled components) are not creating an undesirable and hard to identify
problem when there is no assurance that the version is the same for all
components being consumed by an application.
Is it possible your current scripts can lock each components to the
exact same version of coupled and/or optional components in the same
PEAR installed library?
-ralph
till wrote:
On Fri, Jul 10, 2009 at 4:35 PM, Matthew Weier
O'Phinney<matt...@zend.com> wrote:
-- Саша Стаменковић <umpir...@gmail.com> wrote
(on Friday, 10 July 2009, 11:40 AM +0200):
Thinking about building custom downloader, which will build download with
dependencies, will anyone use it?
Maybe this can be added to Zend_Tool and then used on zend website...
If we go this route, we'll utilize a PEAR channel instead of
re-inventing the wheel.
However, it will take some work for us to determine what constitutes an
individual package, and how to specify the dependencies -- and as that
will likely be a fairly large task, it's been a backburner task for some
time as a result. Any solution we come up with will need to be
automated, to ensure that we don't need to manually determine this
information for each new component, or when component features change.
Would anyone like to start working on such a project?
I have a script that is 99% done. Splits up top-level components into
pear packages. I could contribute that if wanted. I didn't know Zend
wanted a PEAR channel for the Zend Framework.
Till
