From owner-freebsd-questions@FreeBSD.ORG Wed May 30 23:21:40 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1C80B16A41F for ; Wed, 30 May 2007 23:21:40 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id EA24413C46A for ; Wed, 30 May 2007 23:21:39 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 6DD135190F for ; Wed, 30 May 2007 19:21:38 -0400 (EDT) Date: Thu, 31 May 2007 00:21:34 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20070531002134.244afb82@gumby.homeunix.com.> In-Reply-To: <98C46AC6-2999-48D0-AF1C-6BF29221BC20@cox.net> References: <46529E35.7080401@ant.uni-bremen.de> <20070523031505.3071bc9b@gumby.homeunix.com.> <4653F303.2000302@ant.uni-bremen.de> <20070524002531.3cd65668@localhost> <20070523181943.1a97605c@gumby.homeunix.com.> <98C46AC6-2999-48D0-AF1C-6BF29221BC20@cox.net> X-Mailer: Claws Mail 2.9.2 (GTK+ 2.10.12; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: "portmanager -s" deletes ports? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 May 2007 23:21:40 -0000 On Tue, 29 May 2007 21:08:23 -0700 Matthew Navarre wrote: > From the portmanager(1) man page: > -s or --status > status of installed ports > > Says *nothing* about even the possibility of removing installed > ports. Just status. If -s is removing installed ports which have > been moved/removed from the ports tree without confirmation then > it's broken, plain and simple. When I noticed a serious bug in portmanager, I found the source of the problem and submitted a patch - I suggest you do the same. > portmanager also has -s -l *AND* -sl options^Wcommands. -sl has not > a thing to do with -s or -l. Broken by design. -sl should by > convention be equivalent to -s -l, instead -sl maps to --show-leaves > while -s maps to --status and --l maps to log. Lame. It doesn't process its arguments with getopt - so what? I trust you've volunteered your services to help polish it up, otherwise comments like "Broken by design" and "Lame" on someone else's hard work are likely to earn you the contempt you deserve.