[PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)
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. Someone called? Heck yes, willing. Able, most probably, with some help on how to set up things right for PEAR. Emile -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)
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. Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4/ext/midgard config.m4)
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. Emile -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)
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 waiting for a certain particular development to happen isn't usually beneficial. If there'll be people working on PEAR modules, the incentive for the 'pear' utility author will be much higher to make it work, and he may also have some support from others. It's been 14 months since PEAR was born, I think it may be a good idea to try and let it walk a bit. Zeev At 02:11 20/3/2001, Rasmus Lerdorf wrote: See pear/scripts/pear The framework is there. On Tue, 20 Mar 2001, 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. Zeev -- Zeev Suraski [EMAIL PROTECTED] CTO co-founder, Zend Technologies Ltd. http://www.zend.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)
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 midgard folks are the right people to push this along, if they are willing and able. Isn't php-gtk done like the way the PEAR (C) components should be done? At least that's how I compiled that extension. Separately from PHP. Using phpize. So I would guess having e.g. midgard outside PHP shouldn't matter at all? Before separating PEAR from PHP CVS several serious problems should be solved. First and main problem is the building environment. I've already did a post on php-dev@ which describes this problem several weeks ago so I'll just outline a problem: if extension uses several PHP_ARG_WITH or PHP_ENABLE to tune behaviour (=which part to compile in), all of them will be compiled in regardless of user selection. That's due erroreous code which decides that if $php_always_shared set to 'yes', then all $PHP_BLAH should be set to 'yes'. 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. True, true. :) Readline is an example of such extension which fail to compile right now as self contained extension (PEAR module). -- Sincerely yours, Alexander Bokovoy The Midgard Project | www.midgard-project.org |Aurora RD team Minsk Linux Users Group |www.minsk-lug.net| www.aurora-linux.com ALT Linux Team |www.alt-linux.org| Architecte Open Source -- Dijkstra probably hates me (Linus Torvalds, in kernel/sched.c) -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
