<TONGUE_IN_CHEEK>Really what we should do is in the configure process, if --with-dom is specified and not found on the system, we could call wget, untar, ./configure make, etc. It's the same right? Oh, then we depend on wget being installed.</TONGUE_IN_CHEEK>
What is the status quo? If you install perl on a system, it runs out of the box right? Sure, well so does php, except that expat is required to build php, so it's bundled. Now, when you install a perl module, you also have to install the libraries upon which it depends. That's only fair. It's the accepted status quo. Effort would far better be spent creating an extension dependency tree page that links to the libxml page so that if one wants to install an extension, he or she knows exactly where to go to get the libraries that they depend on. No suprises, no gimmicks. Now on Windows or similar systems, where the average user is not used to system administration (witness the number of codered attacks still going around), we can pack all these dependant binary libraries into the installer. I'm not sure who builds the installer, but I know I could make one in no time flat, and would be willing to do so (and even automate a build process if necessary). -1 on the bundling idea. +1 for choice. +1 for binary bundling on Windows. Joseph > -----Original Message----- > From: Zeev Suraski [mailto:[EMAIL PROTECTED]] > Sent: Friday, May 31, 2002 11:05 AM > To: Dan Kalowsky > Cc: brad lafountain; PHP Development Mailing list > Subject: Re: [PHP-DEV] bundling libxml2 / bundling locations > > > At 11:39 PM 5/30/2002, Dan Kalowsky wrote: > >On Thu, 30 May 2002, brad lafountain wrote: > > > > > I personally will take responsiblity for bundling and upgrading it. > > > >As Rasmus stated earlier the reason the MySQL stuff is bundled is due to > >an assurance from the MySQL developers to keep it updated. > > I don't think such an assurance existed to begin with, and whether it > existed or not, it definitely wasn't the case in the beginning, > and I'm not > sure how well it's going now. We bundled it not because of any > assurance, > but because we decided it was important, and we were fed off the "Call to > undefined function" calls on php-general. > > I don't see why it's a problem to bundle libxml2 at all. It doesn't have > to be in our CVS, we can integrate it into the makedist > procedure, provided > Brad can automate his trim-down process. > > Zeev > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
