I was talking with George about this at lunch today. If we really really do require the new version, then we should add a configure check to enforce it, otherwise we should use appropriate #ifdefs.
Why? Everytime we go to upgrade PHP, we find that we need to upgrade libxml2 as well. While it's fine for PHP to use that, what about other packages that also require libxml2? The paranoid sysadmin inside us feels reluctant/worried at that prospect. We (PHP) have had a similar issue with libcurl requirements in the past too, to the point where I just stopped enabling it (things were worse there though, as the download from sf.net was really unpredictable and made it very difficult to get hold of the latest and greatest). So, my 2 cents are: if it's too much trouble to maintain those ifdefs, bump the minimum requirements, otherwise, let's try to keep it flexible. --Wez. On Tue, 15 Feb 2005 02:01:13 +0100, Christian Schneider <[EMAIL PROTECTED]> wrote: > Andi Gutmans wrote: > > What's the status of 2.6.x in Linux distributions? Is it already > > standard in the latest SUSE/Redhat distros? > > SuSE 8.1: libxml2-2.4.23 > SuSE 8.2: libxml2-2.5.3 > SuSE 9.0: libxml2-2.5.10 > SuSE 9.1: libxml2-2.6.7 > SuSE 9.2: libxml2-2.6.12 > > I'd say that at least SuSE 8.2 and 9.0 are still quite common though. > > - Chris > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php