Date: Thu, 24 Mar 2016 02:33:40 +0100 From: Guido Falsi <mad@madpilot.net> To: Mike Jakubik <mike.jakubik@intertainservices.com> Cc: Ports <ports@freebsd.org> Subject: Re: mail/roundcube (bsd.php.mk broken?) Message-ID: <56F343F4.1080603@madpilot.net> In-Reply-To: <0ad88e191dc0cdf48ad3dda64fe4425d@intertainservices.com> References: <ae9070e3746fe0597adf143df75ef9b7@intertainservices.com> <56F3111B.4030901@madpilot.net> <3f72fc0f07e217ddb36190fa46b75d35@intertainservices.com> <56F33802.4070100@madpilot.net> <0ad88e191dc0cdf48ad3dda64fe4425d@intertainservices.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/24/16 01:56, Mike Jakubik wrote: > On 2016-03-23 08:42 PM, Guido Falsi wrote: >> On 03/24/16 01:09, Mike Jakubik wrote: > >>> ports tree. I guess i can try upgrading to 5.5 and hope that my >>> applications are compatible with it. Sigh, FreeBSD has become a PITA >>> lately to maintain unless everything installed is bleeding edge. In any >>> case, thanks for the help. >> >> Sorry I beg to disagree. >> >> php 5.4 is unsupported upstream, and 5.5 will EOL in a few months. You >> should complain to the php project about this, not the ports tree, which >> is just complying with upstream. > > You are correct, however I think php is a special case, because it's a > slow adopter, sadly a lot of hosting providers have not updated and a > lot of software is still not compatible with the latest versions. For > example, the default version of php in CentOS 7 is still 5.4, so I don't > see why removing it from ports was a good idea. > The reason is it is not supported, bugs and vulnerabilities are not fixed, we would end up giving potentially insecure software, or even worse, software with known vulnerabilities. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56F343F4.1080603>