Re: cvs: php4 / acinclude.m4 configure.in /build build.mk
| From: | Jani Taskinen | Date: | Sat, 03 May 2003 23:01:16 +0000 |
| Subject: | Re: cvs: php4 / acinclude.m4 configure.in /build build.mk | ||
| References: | 1 2 3 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-20664@lists.php.net to get a copy of this message | ||
On 2 May 2003, Sterling Hughes wrote:
>On Fri, 2003-05-02 at 06:20, Jani Taskinen wrote:
>> I don't see any agreement anywhere about this..why did you
>> commit this crap anyway?
>>
>> You never explained what the possible use of '--disable-bundle-all'
>> might be? (whatta hell does it?) Is it related to MacOSX somehow?
>> As it has *.bundle libs..
>>
>
>--disable-bundle-all is just in there as sugar. However, I think its
>useful. It allows you to remove all bundled libraries from PHP, and
>therefore forces you to manually satisfy all library dependencies.
--disable-all does this already.
>:) The idea is that I want the extensions to be separate from the
>libraries that they bundle. For example (although, atm we don't have
>anything that really takes advantage of this), I might want to not have
>ext/xml, but I would want ext/wddx and ext/libxmlrpc.
Huh? If I want only xmlrpc, I don't need to compile ext/xml.
It has been like that all the time. ext/wddx is propably enabling
ext/xml just because the person who wrote it was lazy.
>Or, going into the useful, I might want to switch the underlying
>implementation of all these things to use libxml2, when that becomes
>bundled (again, a different argument for a different time.) php5/bundle
>allows this to be cleanly implemented (and *quite* a few people have
>shown that they want it).
I have nothing against that, like I said before, but I don't see
the need to add these useless configure options.
--Jani