Re: Re: PEAR (was: Re: [PHP-CVS] cvs: php4/ext/midgard config.m4)
| From: | Rasmus Lerdorf | Date: | Tue, 20 Mar 2001 00:22:55 +0000 |
| Subject: | Re: Re: PEAR (was: Re: [PHP-CVS] cvs: php4/ext/midgard config.m4) | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-49436@lists.php.net to get a copy of this message | ||
> 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 about this. If it won't be simple, it will
> > simply not be. We can start simple, and work our way up.
>
> For unixoids, this could probably be a glue script that uses CVS.
> There'd
> probably need to be checkin-time phpize setup or somesuch to make it
> distribution-ready, or people would need autoconf et al on their systems
> allways.
>
> I don't know how this would work for windows system, though.
Well, just like the snapshots at snaps.php.net, any C extensions should be
pre-autoconfed and should not require it on the user end. And no, we
don't want to do software distribution via cvs. Straight HTTP should be
fine.
-Rasmus