My experience with pear is that it can work great, but on the other
hand the distribution system is not always fully functional on all
comp's php runs on, or outdated, or simply unknown by the admins..
even more challenging when the user only has ftp access or something
to the host he's deploying on :)
Such troubles in the past have kind of taught me to avoid it where i
could
On Jun 6, 2008, at 7:44 PM, Ropu wrote:
hmmm, i think for the same reason we have a subset of Zend
to have less dependencies.
ropu
On Fri, Jun 6, 2008 at 10:40 AM, Kevin Brown <[EMAIL PROTECTED]> wrote:
Actually -- is this available in PEAR? If so, why not just mention
grabbing
it from there?
On Fri, Jun 6, 2008 at 10:38 AM, Kevin Brown <[EMAIL PROTECTED]> wrote:
I only mean for the distributable (probably a tar ball file for
PHP),
once
we get to releases.
I'd rather live with large downloads than live without tests.
On Fri, Jun 6, 2008 at 10:16 AM, Chris Chabot <[EMAIL PROTECTED]>
wrote:
As far as i know it is pretty much the only option ... well we
could add
a
readme saying 'download this, unpack it there, run these commands
to
integrate it; And then you can test" but that would probably
really take
the
spontaneity out of testing wouldn't it.. but it is an option i
guess.
On Jun 6, 2008, at 7:12 PM, Kevin Brown wrote:
Is importing all of PHPUnit really the only viable option? We'll
definitely
want to make sure that any releases of the PHP code in the
future have
an
option of only downloading the source and not phpunit -- that's
a lot
of
code!
On Fri, Jun 6, 2008 at 8:02 AM, Chris Chabot <[EMAIL PROTECTED]>
wrote:
Still catching up with patches and filing bugs for the open to-do
items...
In doing so the list got a bit flooded as I'm making my way
through
this, my
apologies!
-- Chris
--
.-. --- .--. ..-
R o p u
