From owner-freebsd-ports@freebsd.org Fri Dec 16 15:54:05 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 29935C80038 for ; Fri, 16 Dec 2016 15:54:05 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1681687A for ; Fri, 16 Dec 2016 15:54:05 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: by mailman.ysv.freebsd.org (Postfix) id 15D69C80034; Fri, 16 Dec 2016 15:54:05 +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 157E1C80033 for ; Fri, 16 Dec 2016 15:54:05 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E892E879 for ; Fri, 16 Dec 2016 15:54:04 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id 14D6543C3B; Fri, 16 Dec 2016 09:52:49 -0600 (CST) From: John Marino Reply-To: marino@freebsd.org To: "ports@FreeBSD.org Ports" , Roger Marquis Subject: The ports collection has some serious issues Message-ID: <5c6df0ce-a473-d125-10a0-71b95a83512b@marino.st> Date: Fri, 16 Dec 2016 09:53:56 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161216-0, 12/16/2016), Outbound message X-Antivirus-Status: Clean X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 15:54:05 -0000 Roger Marquis wrote >> It is every week. Consider the FreeBSD forums as well. >> "misuse" and "misunderstanding" failures are attributed to the tool. Let's >> stop making excuses for portmaster. It is what it is and we've had years to >> evaluate it. > > If portmaster was part of base I'd agree that it should be deprecated, > however, being a port it can be afforded more leeway. All portmaster > needs IMO is a strong WARNING message to be displayed on installation A) > enumerating some of the potential bugs and B) clarifying that portmaster > is third party software that is neither actively maintained nor > supported (or recommended?) by FreeBSD. It is just semantics. A "deprecated" message is just a warning. Maybe even a "strong" warning. By itself, it means nothing more than that. Since the beginning, portmaster was not going to be removed, it was just going to carry this warning to alert users. What you propose is what has always been proposed. I never understood why people went ape-**** over it, unless they don't understand what "deprecated without expiration" actually means. I just assumed that having such a warning was a scarlet letter and fans of portmaster didn't want the reputation defamed. If Torsten drops maintainership then some sort of "strong" warning should come with that drop. I would be satisfied with adding a descriptive DEPRECATED message myself. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus