From owner-freebsd-ports@FreeBSD.ORG Mon Jan 25 18:36:13 2010 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B101A10656C5 for ; Mon, 25 Jan 2010 18:36:13 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 5BE758FC1A for ; Mon, 25 Jan 2010 18:36:13 +0000 (UTC) Received: (qmail 21219 invoked by uid 399); 25 Jan 2010 18:36:12 -0000 Received: from localhost (HELO ?192.168.0.110?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 25 Jan 2010 18:36:12 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B5DE49B.60409@FreeBSD.org> Date: Mon, 25 Jan 2010 10:36:11 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: Miroslav Lachman <000.fbsd@quip.cz> References: <4B585FC6.4020602@quip.cz> <4B58789B.4050303@FreeBSD.org> <4B5DD541.70906@quip.cz> In-Reply-To: <4B5DD541.70906@quip.cz> X-Enigmail-Version: 1.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Cc: "freebsd-ports@FreeBSD.org" Subject: Re: portmaster and meaning of --show-work X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2010 18:36:13 -0000 On 1/25/2010 9:30 AM, Miroslav Lachman wrote: > Doug Barton wrote: > >> Funny you should mention that. :) The current svn version of portmaster >> (users/dougb/portmaster) has this exact feature, and it's almost ready >> to be committed to the port. It's currently on by default, and I just >> need to add a knob to disable it, and some code to override it if the >> only thing to do is the one port the user specified on the command line. >> I may get to that today, but $REALLIFE has been kicking my *hrmph* >> lately, so it may not be done till the weekend. I would appreciate it if >> you would give that a look and tell me if it suits your needs. It's >> likely that once I'm 100% convinced that this new feature is the right >> way to go that I will drop the --show-work option altogether. > > I upgraded to portmaster-2.17 with this new feature and it is really nice! Thanks. :) > One little idea to next improvement (and next work for you ;]) > There can be some configuration variable / env. variable to control the > situation when "proceed" question will be asked: > 1] always It's on by default except for the case where you specify one or more ports on the command line and those are the ONLY things that will happen. In that case it doesn't seem necessary to prompt the user. > 2] only if something new will be installed > 3] never "Never" can be done with the --no-confirm option, or by placing the appropriate value in .portmasterrc (see the man page). > And one more question - how hard (for you / portmaster) is to monitor > changes of dependencies before/after upgrade of some port? It can be > useful if portmaster can report dependencies which will not be needed > after upgrade (as part of the final report = after "The following > actions were performed" list) The -s feature already exists for this. I don't think it would be generally useful to run this code after every use of portmaster since the trend is for dependencies to go up, not down. But I do recommend that people use the -e feature when they uninstall ports which does run -s for them when they are done. hth, Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso