From owner-freebsd-ports@FreeBSD.ORG Fri Nov 6 17:41:46 2009 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5670D1065672 for ; Fri, 6 Nov 2009 17:41:46 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id DA1BF8FC12 for ; Fri, 6 Nov 2009 17:41:45 +0000 (UTC) Received: (qmail 27339 invoked by uid 399); 6 Nov 2009 17:41:45 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 6 Nov 2009 17:41:45 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4AF45FDF.4030800@FreeBSD.org> Date: Fri, 06 Nov 2009 09:41:51 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Miroslav Lachman <000.fbsd@quip.cz> References: <200911051539.21097.oliver@realtsp.com> <4AF4110C.6060501@FreeBSD.org> <4AF4308B.4080905@quip.cz> <4AF43319.1010909@FreeBSD.org> <4AF44DE2.2040304@quip.cz> In-Reply-To: <4AF44DE2.2040304@quip.cz> X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, alistair@realtsp.com, Oliver Schonrock , Alex Dupre Subject: Re: FreeBSD Port: php5-5.2.11_1 upgrade path to 5.3.0/1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 17:41:46 -0000 Miroslav Lachman wrote: > Even if there are just a "few" incompatibilities, it means some clients > applications on webhosting will stop working and clients will scream on > helpline right after the update of the servers PHP... Sounds like you're familiar with the problems, why don't you volunteer to maintain the 5.2.x set of ports after a fork? Now both problems are solved. :) And yes, I'm serious, assuming that there will be updates in the 5.2.x series that users will need. If not, simply not updating their existing ports is a reasonable solution. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/