From owner-freebsd-ports@FreeBSD.ORG Fri Jan 14 14:22:39 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A59316A4CE; Fri, 14 Jan 2005 14:22:39 +0000 (GMT) Received: from mail.vslash.com (gambetta-2-82-67-185-6.fbx.proxad.net [82.67.185.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 746C243D55; Fri, 14 Jan 2005 14:22:38 +0000 (GMT) (envelope-from valery@vslash.com) Received: from [192.168.0.22] (oxe [192.168.0.22]) by mail.vslash.com (Postfix) with ESMTP id 6D9991DA00; Fri, 14 Jan 2005 15:25:59 +0100 (CET) Message-ID: <41E7D58B.8020905@vslash.com> Date: Fri, 14 Jan 2005 15:22:03 +0100 From: =?UTF-8?B?VmFsw6lyeQ==?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maxim Sobolev References: <41E7AF5A.3020603@portaone.com> In-Reply-To: <41E7AF5A.3020603@portaone.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: ports@freebsd.org cc: ale@freebsd.org Subject: Re: PHP ports/packages framework is seriously flawed X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 14:22:39 -0000 Hi, 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, 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. 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, ...). More, you can patch your php without waiting a new port, and this is important for security. In my point of view, i think that with a solution like php, you must know everithing about it, specially at the build time, this is very important if you want to be accurate, and know why you get an error using a functionnality ; you'll win time. Well, try to compile it yourself, and see what you want. i hope this help you, br v/ Maxim Sobolev wrote: > Hi guys, > > Maybe I am missing something obvious, but as long as I can see, the > whole PHP framework is currently severely flawed. Specifically I am > talking about www/mod_php4 port/package. Current system doesn't allow > any PHP extensions to be installed for it, at the same time when > building mod_php4 it explicitly disables all possible extensions, so > that resulting module is nearly useless since it lacks even essential > functions and it's impossible to install them later on. > > Perhaps FreeBSD PHP maintainers should take a closer look on how this > problem is addressed in major linux distros. > > Regards, > > Maxim > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >