From owner-freebsd-ports@freebsd.org Thu Dec 15 16:29:29 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 A9BDDC811B8 for ; Thu, 15 Dec 2016 16:29:29 +0000 (UTC) (envelope-from wblock@wonkity.com) 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 9390CD03 for ; Thu, 15 Dec 2016 16:29:29 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: by mailman.ysv.freebsd.org (Postfix) id 92E9CC811B7; Thu, 15 Dec 2016 16:29:29 +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 92978C811B6 for ; Thu, 15 Dec 2016 16:29:29 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6587ED02 for ; Thu, 15 Dec 2016 16:29:28 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id uBFGTQHf098352 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 15 Dec 2016 09:29:26 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id uBFGTQrg098349; Thu, 15 Dec 2016 09:29:26 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Thu, 15 Dec 2016 09:29:26 -0700 (MST) From: Warren Block To: RW cc: ports@freebsd.org Subject: Re: The ports collection has some serious issues In-Reply-To: <20161215155139.4a3d6033@gumby.homeunix.com> Message-ID: References: <20161208085926.GC2691@gmail.com> <20161215155139.4a3d6033@gumby.homeunix.com> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.1 (wonkity.com [127.0.0.1]); Thu, 15 Dec 2016 09:29:27 -0700 (MST) 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: Thu, 15 Dec 2016 16:29:29 -0000 On Thu, 15 Dec 2016, RW via freebsd-ports wrote: > On Thu, 15 Dec 2016 07:40:46 -0700 (MST) > Warren Block wrote: > >> On Thu, 8 Dec 2016, Matt Smith wrote: >> >>> On Dec 08 05:16, Daniil Berendeev wrote: >>>> >>>> Although portmaster is not releated to the FreeBSD project and is >>>> an outside tool, there aren't any alternatives from the project >>>> itself. So use it or die. Not a nice situation. >>> >>> People have been trying to get portmaster deprecated and removed >>> from the handbook but have met with resistance. >> >> Well, yes. Because it works, has no dependencies, and there is no >> equivalent replacement. Except maybe portupgrade, which has legacy >> problems like poor default options. > > That's a very minor issue, and an absurd excuse to rule-out portupgrade. I didn't rule it out. Portupgrade gets some of the defaults wrong, like not running all the 'make config' steps first. That's a legacy issue because if the default changes, it could conceivably cause problems for existing users. Beyond that, other than a dependency on Ruby, portupgrade at least exists in the same space as portmaster.