From owner-freebsd-ports@freebsd.org Thu Mar 24 16:54:51 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F6DBADC651 for ; Thu, 24 Mar 2016 16:54:51 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3A6A51279 for ; Thu, 24 Mar 2016 16:54:51 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: by mailman.ysv.freebsd.org (Postfix) id 39BF6ADC650; Thu, 24 Mar 2016 16:54:51 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36C42ADC64E; Thu, 24 Mar 2016 16:54:51 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B972F1278; Thu, 24 Mar 2016 16:54:49 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id E47E72840C; Thu, 24 Mar 2016 17:54:45 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 7FA6828429; Thu, 24 Mar 2016 17:54:44 +0100 (CET) Message-ID: <56F41BD4.9050306@quip.cz> Date: Thu, 24 Mar 2016 17:54:44 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Mike Jakubik , Guido Falsi CC: Ports , owner-freebsd-ports@freebsd.org Subject: Re: mail/roundcube (bsd.php.mk broken?) References: <56F3111B.4030901@madpilot.net> <3f72fc0f07e217ddb36190fa46b75d35@intertainservices.com> <56F33802.4070100@madpilot.net> <0ad88e191dc0cdf48ad3dda64fe4425d@intertainservices.com> <56F343F4.1080603@madpilot.net> <7e95d28f975984bf195af16b2f8ef071@intertainservices.com> In-Reply-To: <7e95d28f975984bf195af16b2f8ef071@intertainservices.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2016 16:54:51 -0000 Mike Jakubik wrote on 03/24/2016 17:11: > 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 >>>>> 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. > > 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. You should read UPDATING before each update / upgrade and you can use 'pkg updating' command for it. Ports are constantly moving. Almost every minute there is some changes in ports (dependencies of another ports), ports framework, pkg util etc. It is not easy to maintain huge ports with so many dependencies like PHP and if nobody watns to maintain it, then it must be removed. PHP 5.3 was adopted by another maintainer and kept alive for about year after being discontinued upstream but nobody steped in to do this for PHP 5.4. There are about 25 000 ports and each must have somebody to maintain it. There is no reason to have dead unmaintained ports in a tree. When I wanted to resurrect removed port pnm2ppa I must become a maintainer - and that's right. Miroslav Lachman