Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)

2001-03-19 Thread Alexander Bokovoy
On Tue, Mar 20, 2001 at 01:00:15AM +0100, Jani Taskinen wrote: > On Mon, 19 Mar 2001, Rasmus Lerdorf wrote: > >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 midg

Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4/ext/midgard config.m4)

2001-03-19 Thread Jani Taskinen
On Tue, 20 Mar 2001, Emiliano wrote: >Zeev Suraski wrote: >> >> At 02:04 20/3/2001, Rasmus Lerdorf wrote: >> >No, we need tighter integration. We want to be able to do something along >> >the lines of "pear pear.php.net/midgard" and it would go and fetch >> >the the component, build it and insta

Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)

2001-03-19 Thread Zeev Suraski
That's great, but it shouldn't be the starting point for the project... Jani is right that whenever we speak about separating PEAR, or putting extensions in it, it's always at some point in the future. Opensource projects usually start up and roll once they reach some critical mass, and waiti

Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4/ext/midgard config.m4)

2001-03-19 Thread Rasmus Lerdorf
> Zeev Suraski wrote: > > > > At 02:04 20/3/2001, Rasmus Lerdorf wrote: > > >No, we need tighter integration. We want to be able to do something along > > >the lines of "pear pear.php.net/midgard" and it would go and fetch > > >the the component, build it and install it. > > > > I completely agre

Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4/ext/midgard config.m4)

2001-03-19 Thread Emiliano
Zeev Suraski wrote: > > At 02:04 20/3/2001, Rasmus Lerdorf wrote: > >No, we need tighter integration. We want to be able to do something along > >the lines of "pear pear.php.net/midgard" and it would go and fetch > >the the component, build it and install it. > > I completely agree with Andi ab

Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)

2001-03-19 Thread Zeev Suraski
At 02:04 20/3/2001, Rasmus Lerdorf wrote: >No, we need tighter integration. We want to be able to do something along >the lines of "pear pear.php.net/midgard" and it would go and fetch >the the component, build it and install it. I completely agree with Andi about this. If it won't be simple, i

[PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)

2001-03-19 Thread Emiliano
Rasmus Lerdorf wrote: > 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. Some

[PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)

2001-03-19 Thread Zeev Suraski
I agree. At 01:33 20/3/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

[PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)

2001-03-19 Thread Rasmus Lerdorf
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 o