Date: 03/19/01
- Next message: Rasmus Lerdorf: "Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)"
- Previous message: Emiliano: "[PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)"
- In reply to: Rasmus Lerdorf: "[PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)"
- Next in thread: Rasmus Lerdorf: "Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)"
- Reply: Rasmus Lerdorf: "Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)"
- Reply: Alexander Bokovoy: "Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 19 Mar 2001, Rasmus Lerdorf wrote:
>Because the whole point of this was to make life easier on midgard users.
So you're saying that every widely used external (at the moment)
php-extension should be put into PHP CVS? :)
>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.
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?
>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. :)
>I've been fiddling with a TiVo extension that would also fit better in
>PEAR than in the main PHP distribution.
And there are also these Windows-only extensions, com , dotnet (?),
printer. Hmm, now that I remember..IMO we should create some better tree
structure into the ext/ dir. ie.
ext/dbms/
oci8
mysql
pgsql
.
.
ext/xml/
sablot
qtdom
dom
.
.
ext/windows/
:)
Or is this a bad idea?
--Jani
>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 <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: Rasmus Lerdorf: "Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)"
- Previous message: Emiliano: "[PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)"
- In reply to: Rasmus Lerdorf: "[PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)"
- Next in thread: Rasmus Lerdorf: "Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)"
- Reply: Rasmus Lerdorf: "Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)"
- Reply: Alexander Bokovoy: "Re: [PHP-DEV] Re: PEAR (was: Re: [PHP-CVS] cvs: php4 /ext/midgard config.m4)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

