Because the whole point of this was to make life easier on midgard users.
And there are a lot of them.  There are not a lot of php-gtk users out
there, and people interested in php-gtk don't tend to need as much
handholding as midgard users.

Having midgard in the PEAR infrastructure makes sense once the PEAR
infrastructure is such that it is easy to install PEAR components that
include C bits.  And yes, perhaps the midgard folks are the right people
to push this along, if they are willing and able.

Another motivator is the readline extension.  Get that into PEAR as a
separate easily installable PEAR component and make it LGPL'ed and we
avoid any Stallman hassles on that particular extension.

I've been fiddling with a TiVo extension that would also fit better in
PEAR than in the main PHP distribution.


On Tue, 20 Mar 2001, Jani Taskinen wrote:

> On Mon, 19 Mar 2001, Rasmus Lerdorf wrote:
> >PEAR will be separate at some point, but let's not go overboard here.  The
> >midgard stuff adds a total of 76K to the tar.gz file.  Big deal.
> I was talking in general, not only midgard. The pear stuff takes
> a lot more than 76k..and this has been pushed further and further into
> the future EVERY time it's talked about. So why not make it a separate
> (pear) module in CVS now? It isn't something that HAS to be in, or is it?
> And if we continue distributing it with PHP we never get PEAR to be
> what it should be. If the answer still is "at some point", why not add
> the php-gtk to the PHP distribution too? :) (I don't want that to happen..)
> --Jani

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to