Re: libxml bundling

Hi My 2 cents on the whole story: libxml2 is a very stable library with almost no API changes (actually Daniel Veillard is very against changing API) and very often releases with feature enhancements, bug fixes and speed improvements. The stable API really does help. We can keep the needed version of libxml2 quite low, except if we introduce newly integrated features (Which will happen with the new domxml extension..). Therefore we don't rely much on a special libxml2 version, just newer than the minimal requierement and that's no problem for configure to check (and I really don't know of any showstopper bugs of libxml2 since I started with domxml) In my opinion, putting libxml2 into CVS was a very bad idea (maintenance et al.), but I see some reasons for bundling it. So why not just add it to the .tgz files during a release or even after buidling the snaps. Snaps-unstable would take the latest (or almost latest) libxml2 stuff, snaps-stable and RC releases use a "freezed"-version. CVS Users should anyway know what they're doing. And whoever wants the latest libxml2 library already installed on his system, should still be able to use that. chregu