Re: cvs: php4 / acinclude.m4 configure.in /build build.mk
| From: | Sterling Hughes | Date: | Fri, 02 May 2003 13:37:34 +0000 |
| Subject: | Re: cvs: php4 / acinclude.m4 configure.in /build build.mk | ||
| References: | 1 2 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-20658@lists.php.net to get a copy of this message | ||
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.
There was agreement on php5-dev@ awhile ago, and no one complained on
internals@, and its important for the xml stuff (next battle, I guess.
:) 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.
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).
-Sterling
--
"First they ignore you, then they laugh at you,
then they fight you, then you win."
- Gandhi