Date: Fri, 06 Nov 2009 09:41:51 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: ports@freebsd.org, alistair@realtsp.com, Oliver Schonrock <oliver@realtsp.com>, Alex Dupre <ale@FreeBSD.org> Subject: Re: FreeBSD Port: php5-5.2.11_1 upgrade path to 5.3.0/1 Message-ID: <4AF45FDF.4030800@FreeBSD.org> In-Reply-To: <4AF44DE2.2040304@quip.cz> References: <200911051539.21097.oliver@realtsp.com> <4AF4110C.6060501@FreeBSD.org> <4AF4308B.4080905@quip.cz> <4AF43319.1010909@FreeBSD.org> <4AF44DE2.2040304@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AF45FDF.4030800>