Date: Fri, 17 Nov 2006 07:03:36 -0800 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: Andy Fawcett <andy@athame.co.uk> Cc: Ivan Voras <ivoras@fer.hr>, freebsd-ports@freebsd.org Subject: Re: FreeBSD 6.1-R-p10 and PHP 5.2.0 Message-ID: <20061117150336.GA89839@icarus.home.lan> In-Reply-To: <200611171322.14121.andy@athame.co.uk> References: <200611161509.53708.josh@tcbug.org> <ejk41b$2mv$1@sea.gmane.org> <200611171322.14121.andy@athame.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061117150336.GA89839>