Hello,
I am glad to see ZF on a PEAR channel.
However, I feel there are some advantages to distributing in micro
packages versus a single macro package. Mostly, that distributing
smaller packages forces an explicit enumeration of dependencies
between packages. I believe the process of
I see much value in each of the following scenarios, which combined form
what I expect to cover the majority of use cases:
1) PEAR component distributing entire ZF (for developers interested
primarily in the latest official release of the incubator, docs, and
tests, with an easy mechanism to
I forgot to reply to the list.
---BeginMessage---
Solution #2 would be great for silverorange. If we want the latest and
greatest from the incubator packages for our dev servers we can do a SVN
checkout. Also, we love your on-line documentation.
On Fri, 2007-02-02 at 14:05 -0800, Gavin Vess
Matthew Weier O'Phinney wrote:
Just a note: most PEAR packages contain, minimally, tests, and often
documentation and examples.
I only actually discovered this recently when one pear package put it's
docs and tests in c:\php\pear even though my install is in
c:\programs\php\pear ...
Michael Caplan schreef:
Hi Andries,
I would think that distributing via a PEAR channel would help reach a
broader public. Was that not the case?
Not to beat what I assume is a long dead discussion, I don't see the
connection between a need to release the whole codebase in steps VS
making each
Message-
From: Andries Seutens [mailto:[EMAIL PROTECTED]
Sent: February 1, 2007 1:48 PM
To: Michael Caplan
Cc: fw-general@lists.zend.com
Subject: Re: [fw-general] PEAR Channel Distro
Michael Caplan schreef:
Hi Andries,
I would think that distributing via a PEAR channel would help reach
the stated concern about end
developer complications?
Best,
Michael
-Original Message-
From: Andries Seutens [mailto:[EMAIL PROTECTED]
Sent: February 1, 2007 1:48 PM
To: Michael Caplan
Cc: fw-general@lists.zend.com
Subject: Re: [fw-general] PEAR Channel Distro
Michael Caplan schreef
Michael Caplan wrote:
Being a newbie, perhaps I am overlooking something here, but I don't
understand your comment that The Zend Framework works together, as a
complete unit. I understand their are various component dependencies,
but I don't believe that I can't use Zend_Pdf, for example, if
Rob Allen wrote:
Michael Caplan wrote:
Being a newbie, perhaps I am overlooking something here, but I don't
understand your comment that The Zend Framework works together, as a
complete unit. I understand their are various component dependencies,
but I don't believe that I can't use Zend_Pdf,
It seems to me that the biggest hurdle to keeping zend framework up to date
on a pear channel of its own is turning it into a pear package is altogether
too manual.
Have we looked at the difficulty in setting up a phing task to automagically
build the package? It's already done for the
: January 30, 2007 5:19 PM
To: fw-general@lists.zend.com
Cc: Nathan Fredrickson
Subject: RE: [fw-general] PEAR Channel Distro
At silverorange we use some elements from the Zend Framework already.
All our other code is managed through PEAR channels (both ours and
PEAR's) and we'd love it if Zend
Haven't done it myself, but according to this blog it seems possible:
http://urdalen.com/blog/?p=135
From: Daniel O'Connor [mailto:[EMAIL PROTECTED]
Sent: January 31, 2007 7:47 AM
To: fw-general@lists.zend.com
Subject: Re: [fw-general] PEAR Channel Distro
It seems to me
*To:* fw-general@lists.zend.com
*Subject:* Re: [fw-general] PEAR Channel Distro
It seems to me that the biggest hurdle to keeping zend framework up to
date on a pear channel of its own is turning it into a pear package is
altogether too manual.
Have we looked at the difficulty in setting up
Being very new to Zend FW, I'm curious why a maintained and segmented
(IE: each Zend FW component like Zend_Filter available independently)
PEAR distribution hasn't been a core distribution method. It seems like
it would be a logic step considering that Zend FW fits nicely into PEAR
packages. It
Hello,
The priority reason for setting up the PEAR channel, was to reach a
broader public, that would be testing our code, and thus gather more
feedback.
There have been numerous discussions about this in the past, and there
has been decided to stick to the idea of code reales of the whole
as separate PEAR packages.
Best,
Michael
-Original Message-
From: Andries Seutens [mailto:[EMAIL PROTECTED]
Sent: January 30, 2007 12:05 PM
To: Michael Caplan
Cc: Richard Thomas; fw-general@lists.zend.com
Subject: Re: [fw-general] PEAR Channel Distro
Hello,
The priority reason for setting
Subject: Re: [fw-general] PEAR Channel Distro
Hello,
The priority reason for setting up the PEAR channel, was to reach a
broader public, that would be testing our code, and thus gather more
feedback.
There have been numerous discussions about this in the past, and there
has been
17 matches
Mail list logo
