Date: Wed, 27 Jan 2016 07:24:44 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: marino@freebsd.org Cc: Adam Weinberger <adamw@adamw.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r407270 - head/ports-mgmt/portmaster Message-ID: <20160127072444.GA95393@FreeBSD.org> In-Reply-To: <56A86A88.1070908@marino.st> References: <201601261123.u0QBNcvL091258@repo.freebsd.org> <FFDB388E-185C-4A8C-A90A-C61F813B2856@adamw.org> <56A86A88.1070908@marino.st>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 27, 2016 at 07:58:16AM +0100, John Marino wrote: > 1) You are aware that all the commit does is add a warning to portmaster > right? So "the decision" is whether people should be warned that > portmaster doesn't work needs to be a major group discussion. > > 2) no, portmaster does NOT work as intended. It is full of bugs and > people are constantly reporting issues with it. +1 on deprecating portmaster. I've never seen a reason for its existence given that portupgrade is much more robust, featurerich, and intuitive to use (I was not aware that portmaster is so buggy since it never actually worked for me, just kept asking questions). The fact is that we have to provide nearly identical set of commands for both portupgrade and portmaster in UPDATING is ridiculous. May portmaster rest finally in peace please? ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160127072444.GA95393>