mail/roundcube (bsd.php.mk broken?)
mike.jakubik at intertainservices.com
Thu Mar 24 16:11:26 UTC 2016
On 2016-03-23 09:33 PM, Guido Falsi wrote:
> 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
>>>> 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.
>>> should complain to the php project about this, not the ports tree,
>>> 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
>> 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.
I get what you are saying, but I think these kind of changes could be
handled better. You go to update something and shit breaks or you get
some incomprehensible errors such as in this case forcing you to rummage
through some UPDATING file or mailing lists. What ever happened to POLA?
Why couldn't it have prompted me upon trying to perform a minor update
of roundcube that my version of PHP is no longer supported, and perhaps
give me an option to continue anyways at my own risk since it works just
fine with the php i have installed. Now i have to manually reinstall all
the php packages and binaries that depend on them and hope that my php
software will still function with the new php. That is why i say that
FreeBSD is a PITA to maintain.
More information about the freebsd-ports