Date: Fri, 14 Jan 2005 15:50:14 +0100 From: Alex Dupre <ale@FreeBSD.org> To: =?ISO-8859-1?Q?Val=E9ry?= <valery@vslash.com> Cc: Maxim Sobolev <sobomax@portaone.com> Subject: Re: PHP ports/packages framework is seriously flawed Message-ID: <41E7DC26.6040305@FreeBSD.org> In-Reply-To: <41E7D58B.8020905@vslash.com> References: <41E7AF5A.3020603@portaone.com> <41E7D58B.8020905@vslash.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Valéry wrote: > i'm not from FreeBSD, but if i can advise you : > php is *very scalable*, and before having all > options you want, you must build it 5 or 6 times. > I'm using 4.3.4 Then, build it another time, 4.3.4 has a lot of serious bugs. FYI, you can install new extensions without rebuild php, using the ports. > and it was compiled not from > the BSD ports, but from the php.net sources. > The 1st reason is that - i think - a port cannot show > you every configuration you want, specially with > php ; there's a lot of '3rd part software' with > php. Ever tried lang/php4-extensions? > The second one is that compiling php in > this way is not difficult, php is well done, > and well documented, and you'll get > exactly what you expect from php (eg GD, XML, > XSL, CLI or CGI, ...). Same with ports, without messing the filesystem. > More, you can patch your php without waiting > a new port, and this is important for security. Sure, this is the reason you have 4.3.4 version and the port is at 4.3.10, right? :-) -- Alex Dupre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41E7DC26.6040305>