Date: Fri, 12 Jul 2013 07:50:16 -0400 From: Jerry <jerry@seibercom.net> To: freebsd-ports@freebsd.org Subject: Re: postmaster php55 left php5 stuff Message-ID: <20130712075016.373cda3c@scorpio> In-Reply-To: <51DFE0EB.7040305@FreeBSD.org> References: <6AB16718-863B-4BD0-A753-3DBC41D1B09C@kreme.com> <51DFDDF1.4060406@shatow.net> <51DFE0EB.7040305@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 12 Jul 2013 12:56:43 +0200 Alex Dupre articulated: > Yes, there are 10 types of people in the world: who want php port > always updated to the latest branch and who want a new set of phpXX > ports for every branch. > It's impossible to satisfy both types, unless we keep an additional > set of 'php' ports with the same contents of latest 'phpXX' set. While it may be impossible to completely satisfy both groups, it is possible to reach a sensible compromise. Creating a new set of ports for each major update of PHP will allow those who want to use the latest version, no mater what the reason, the able to do so while not causing the users of older versions any significant problem. It is all ready being done with "bash". One maintainer is keeping the older version "maintained" and updating it when ever he feels so inclined, while another maintainer is keeping the port current. These two ports are not causing any problems that I am aware of. I would suggest that a similar plan be instituted for ports that exhibit these same traits. REF: Port: bash-4.2.45 Port: bash-static-4.2.45 Maint: obrien@FreeBSD.org Port: bash-devel-4.2.45_1 Port: bash-static-devel-4.2.45_1 Maint: ehaupt@FreeBSD.org -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130712075016.373cda3c>