From owner-freebsd-ports@freebsd.org Thu Dec 15 15:30:08 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 1F3FDC77883 for ; Thu, 15 Dec 2016 15:30:08 +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 F27A0192C for ; Thu, 15 Dec 2016 15:30:07 +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 5E34D43BDE; Thu, 15 Dec 2016 09:28:51 -0600 (CST) Reply-To: marino@freebsd.org To: FreeBSD Mailing List , wblock@wonkity.com From: John Marino Subject: The ports collection has some serious issues Message-ID: <3959e18e-5819-b2c5-69a9-c71ce1282383@marino.st> Date: Thu, 15 Dec 2016 09:29:59 -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 161215-0, 12/15/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: Thu, 15 Dec 2016 15:30:08 -0000 > 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. Every single week, somebody falsely accuses the ports tree of being broken but the accuser is the only one with the problem. What do they all have in common? They are portmaster users. I'll iterate, saying "portmaster works" means applying a very generous definition of "works". >> The recommended replacements are ports-mgmt/synth and ports-mgmt/poudriere. >> These build an entire package repository that the pkg tool can use but they >> do so in clean chrooted environments, and rebuild everything that's required >> to keep a consistent ABI. Synth is more designed for a single live system >> like a desktop or a single server, whereas poudriere is what the freebsd >> package build clusters use and is more designed for that type of usage. Worth >> taking a look. > > These are package builders. Technically preferable, given adequate disk > space and memory, but not equivalent to portmaster. It's like saying git and svn are not equivalent to cvs. > >> It's a shame the handbook hasn't been updated to give this information. > > Which information, in particular? A section on Poudriere was submitted, > and I spent a fair amount of time editing it and getting it in there. > As far as Synth or other information, I'm not aware of any pending > Handbook or other documentation submissions. for starters: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214679 Previous PRs indicated that recommendations for portmaster and portupgrade were to be removed, but so far this PR has stalled. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus