From owner-svn-ports-head@freebsd.org Wed Jan 27 07:07:29 2016 Return-Path: Delivered-To: svn-ports-head@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 E91FEA6E91D; Wed, 27 Jan 2016 07:07:29 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.net (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 C70C61E5C; Wed, 27 Jan 2016 07:07:29 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [192.168.1.21] (248.Red-83-39-200.dynamicIP.rima-tde.net [83.39.200.248]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 90FAE43BC4; Wed, 27 Jan 2016 01:07:27 -0600 (CST) Subject: Re: svn commit: r407270 - head/ports-mgmt/portmaster To: Martin Wilke References: <201601261123.u0QBNcvL091258@repo.freebsd.org> Cc: ports-committers@freebsd.org, "svn-ports-all@FreeBSD.org" , "svn-ports-head@FreeBSD.org" From: John Marino X-Enigmail-Draft-Status: N1110 Reply-To: marino@freebsd.org Message-ID: <56A86CAD.7030507@marino.st> Date: Wed, 27 Jan 2016 08:07:25 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jan 2016 07:07:30 -0000 On 1/27/2016 2:40 AM, Martin Wilke wrote: > Hi John, > > > I do agree with you regarding the maintainer issue as well the open bug > reports, > but looking at the history [1] it was maintained in the way to keep it > working wiht current > ports. I haven not hit any problem in the past few months with it, so I > am not sure where you > get the idea from its not working with the current ports tree. Where I get the idea is 1) the open bug reports 2) the issues on forums 3) core developers familiar with portmaster that tell me it does not properly support ports. Are you really saying the "fact that you don't have problems" is proof that it's not buggy? It has to work in all use cases, not just simple ones. > > About synth, I have not seen any introduction to any mailing list, there > was no public feedback > from any user so far, also there was no feedback on your project side, I > am not sure if that > is a good idea to "advertise" something what was not widely used by the > community yet. We have this site called http://forums.freebsd.org where synth is well known. There's a thread there 8 pages long (169 replies, 2,463 views). I've gotten plenty of feedback and people are switching from portmaster pretty much immediately. > I personally > don't like the idea of having additionally dependency on a single server > just for a package > update/build tool, but that might be just me. So I'd like to ask you to > back out this commit > or at least remove the synth part for now and get some more testing done > and some feedback from the > community. As I said previously, this commit does not do anything except warn the user about portmaster so they are aware of the serious performance and maintenance issues that it has. There is no expiration date. So I'll end the same way as before: Why would you want to hide this important information from users? Finally: poudriere is non-dependency alternative to portmaster and synth can and should be installed from official packages so the fact it is not a bourne shell script really is not a *practical* issue. John