Re: implementing PEAR feature #6396 properly (enabling PECL exts in php.ini)

From: Date: Mon, 22 May 2006 12:09:46 +0000
Subject: Re: implementing PEAR feature #6396 properly (enabling PECL exts in php.ini)
References: 1  Groups: php.pear.core php.pecl.dev 
Request: Send a blank email to pecl-dev+get-3792@lists.php.net to get a copy of this message
Hi Greg, Sorry for the delay, busy lately... On Wed, 10 May 2006 00:23:22 -0400 greg@chiaraquartet.net (Greg Beaver) wrote: > Hi, > > I am working on a solution for automatically enabling PECL extensions > in php.ini and came up against a shortcoming in package.xml version > 2.0 and would like to address this issue head-on. > > I have 2 questions (I'll summarize and then expound): > > 1) Can we use the <pearinstaller> dep to exclude older installs rather > than bumping package.xml to version 2.1? I do not think so. If we add something or change behaviors/roles, we must bump the version. It is the sanest way to determine the appropriate actions while reading a package.xml file. > 2) Any objections to adding <zendextsrcrelease> and > <zendextbinrelease> to package.xml for PECL packages that distribute > zend extensions like APC/Xdebug? Sounds ok to me. > 1) First of all, I am wary of moving to package.xml 2.1, as this will > simply error out with "no handlers for package.xml 2.1" upon > installation. The solution I'm hoping will solve this issue is to > rely upon the pearinstaller dependency. I just committed code that > will check this value prior to any other validation (and will be in > PEAR 1.4.10), and error out with a message that says "upgrade your > PEAR" rather than the uninformative "no handlers" message. Fixing the error messages (more verbose) is a better way. > This way, we can add tags to package.xml 2.0 without forcing a > package.xml version upgrade. Sound good? We have to upgrade. The annoyance or impacts is minimum. "No handler for this version, please upgrade." could be clear enough. Adding an entry to the FAQ, add the PEAR installer deps to the package, they are all complementary solutions. > 1) new config variable "php_ini" must be set to the absolute path to > php.ini: > > pear config-set php_ini /etc/conf/php.ini > > if it is not set, a message is displayed telling the user to enable > the extension in php.ini manually. > 2) upon installation of a PECL extension that uses package.xml version > 2.0, the extension will be added to php.ini if it is not already > enabled 3) upon uninstallation, it will be removed from php.ini > 4) patch against HEAD of pear-core implementing this is > http://pear.php.net/~greg/zendext.patch.txt I will take a look at the patch later this week. The idea itself is ok. However, I like to be sure there is no side effects or nothing will annoy us for the next 3 years. It is a 1.5.x candidate right? Not 1.4.x? -- Pierre

« previous php.pecl.dev (#3792) next »