From owner-freebsd-stable@FreeBSD.ORG Wed Aug 26 19:59:32 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C42B106568D for ; Wed, 26 Aug 2009 19:59:32 +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 EA68B8FC24 for ; Wed, 26 Aug 2009 19:59:31 +0000 (UTC) Received: (qmail 31351 invoked by uid 399); 26 Aug 2009 19:59:25 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 26 Aug 2009 19:59:25 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4A959417.9000208@FreeBSD.org> Date: Wed, 26 Aug 2009 12:59:19 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Skip Ford References: <4A92F00E.1040705@FreeBSD.org> <20090825100052.9d963401.matheus@eternamente.info> <20090825185513.GA1046@menantico.com> <4A94651B.1030501@FreeBSD.org> <20090826025041.GA975@menantico.com> In-Reply-To: <20090826025041.GA975@menantico.com> X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Nenhum_de_Nos Subject: Re: portmaster not ask for port deletion X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 19:59:32 -0000 Skip Ford wrote: > Doug Barton wrote: >> Yes, unfortunately it's not omniscient. :) > > Well, to be honest, it wouldn't need to be. It would just need a flag > to know when nobody is present from whom to request input, and then take > the default action. That's never going to happen. The default choice is not going to be the right one for some percentage of users. > But, if all input is requested during config, then > that's pointless. Yes, that's the goal. >> Second, without knowing what command line you used I couldn't tell you >> for sure what happened of course, but assuming you used some >> combination of '-af' what you saw was expected behavior. There is a >> conflict (I think a fairly obvious one) between the -f option and >> +IGNOREME. Since different users would have different ideas of how to >> resolve that conflict, portmaster takes the safe path and asks you. > > Well, it wasn't immediately obvious to me that someone would ever want to > mark a port ignore and then want to upgrade it. So, it just seemed like a > silly question to me (and still does to be honest, unless that's the > behavior of portupgrade you're trying to match.) I honestly don't know what portupgrade does in that situation. There are at least 2 classes of users that I am trying to "protect" in this case: 1. Users who believe that -f should override +IGNOREME 2. Users who create an +IGNOREME file for some reason, then forget it's there. One of the problems with writing a tool like portmaster is that a lot of users have very strong ideas about how it should work, and very clear reasons for why they think that their way of looking at it is the right way. :) Unfortunately, there is usually an equal number of users on the other side who feel just as strongly. Doug -- This .signature sanitized for your protection