Date: Fri, 17 Nov 2006 18:33:03 +0200 From: Andy Fawcett <andy@athame.co.uk> To: freebsd-ports@freebsd.org Cc: Jeremy Chadwick <koitsu@freebsd.org>, Ivan Voras <ivoras@fer.hr> Subject: Re: FreeBSD 6.1-R-p10 and PHP 5.2.0 Message-ID: <200611171833.04198.andy@athame.co.uk> In-Reply-To: <200611171819.35194.andy@athame.co.uk> References: <200611161509.53708.josh@tcbug.org> <20061117150336.GA89839@icarus.home.lan> <200611171819.35194.andy@athame.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 17 November 2006 18:19, Andy Fawcett wrote: > On Friday 17 November 2006 17:03, Jeremy Chadwick wrote: > > On Fri, Nov 17, 2006 at 01:22:13PM +0200, Andy Fawcett wrote: > > > This is actually a known problem, documented on the PHP site. > > > > > > My nasty solution to deal with this is to have a "good" copy of > > > extensions.ini saved, and I just copy it over after each update. > > > I only need to modify it after adding or removing extensions. > > > > Can you provide the documentation to this known problem? > > > > Also, ale@, is this issue/known problem handled decently when > > installing a php5 extension via ports? (It doesn't sound like it). > > It almost sounds like we need some additional framework to give > > each extension its own priority, thus when extensions.ini is > > edited, sorting the extensions loaded by their priority. > > See: > > http://www.php.net/manual/en/ref.recode.php > http://www.php.net/manual/en/ref.mysql.php > > for a couple of examples, see the "warning" sections. There are > probably others too, I haven't dug much further. See also http://www.pingle.org/2006/10/18/php-crashes-extensions/ A. -- Andy Fawcett | andy@athame.co.uk | tap@kde.org "In an open world without walls and fences, | tap@lspace.org we wouldn't need Windows and Gates." -- anon | tap@fruitsalad.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200611171833.04198.andy>