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 R&D 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]
