On April 3, 2004 12:05 pm, Andi Gutmans wrote: > We'd need to have someone who'll maintain this by probably having a stable > libXML2 tarball someplace in our CVS, and then change makedist to create > the two packages (one with and one without libXML2). This should make > everyone happy as long as it's properly maintained.
While I am not entirely opposed to the idea of bundling libxml2 if XML extensions that are dependant on it are enabled by default there is 1 problem with this approach. Given our history with bundled libraries (gd, expat, sqlite, etc...) we always tend to lag (often quite a bit) behind the official stable release even if we do sync the libraries relatively frequently the release cycle of the libraries themselves is usually much more frequent then that of PHP. Libxml2 in particular seems to have an extremely active release cycle. Another problem is that bundling of a library prevents an easy upgrade of said library by simply recompiling it, instead entire PHP must be rebuilt. Ilia -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
