Re: Bundling libxml2 default?

On Sat, May 17, 2003 at 10:41:36PM +0300, Zeev Suraski wrote: > At 18:34 17/05/2003, Adam Dickmeiss wrote: > >On Sat, May 17, 2003 at 06:15:37PM +0300, Zeev Suraski wrote: > >> At 10:12 17/05/2003, Sebastian Bergmann wrote: > >> >Derick Rethans wrote: > >> >> Yup, feel free to unbundle libxml again :) > >> > > >> > Why not simply drop *all* bundled libraries (maybe libmysql beeing the > >> > only exception (for historic reasons)) and just require libxml2, pcre, > >> > etc.? > >> > >> Because this is not helpful, short of giving very few people @php.net a > >> warm fuzzy feeling. > >What's your point? > > That we've gone through this discussion a zillion times before. Search the > archives. What's the point of making a comment when you apparently is not willing to discuss this? The problems with bundling becomes more and more apparent, IMHO. Not only makes it PHP more difficult to configure, it also results in more unnecessary work for PHP contributors, since they have to ensure the "latest and greatest". What about security for external bundled software. Will there be a PHP release when vulnerabilities are found in any of those? If no bundling took place updating would in many cases be provided by the OS provider. Even if it doesn't it will mean recompile or refetch a DLL/SO without the need to recompile whole PHP. Now, let's assume for a moment that the PHP code maintainers are still willing to do it. At least the configure options for the components could be harmonized : --with-component Search for component in system directories. If that is not found, use the bundled version (if any). --with-component=bundled Use the bundled version. Suggested by Moriyoshi. --with-component=dir Use the installed component in prefix dir. --without-component Do not use component. -- Adam > Zeev -- Adam Dickmeiss mailto:adam@indexdata.dk http://www.indexdata.dk Index Data T: +45 33410100 Mob.: 212 212 66