Date: Thu, 03 May 2007 20:26:01 -0400 From: Robert Noland <rnoland@2hip.net> To: Avinash Duduskar <avinash.duduskar@gmail.com> Cc: ports@FreeBSD.org Subject: Re: FreeBSD Port: portmanager-0.4.1_9 - broken? Message-ID: <1178238361.60150.15.camel@rnoland-ibm.acs.internap.com> In-Reply-To: <46390a86.5ca00218.5c93.3d87@mx.google.com> References: <46390a86.5ca00218.5c93.3d87@mx.google.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2007-05-03 at 03:32 +0530, Avinash Duduskar wrote: > Hi, > > > I¢m getting the following error when using portmanager: > > barge# /usr/local/bin/portmanager -ui > rParseCommandLine 0.4.1_9 error: /usr/ports/-ui is not a valid port > directory > rParseCommandLine 0.4.1_9 info:either you have used an invalid command line > switch as the first option or you are trying to update a non existent port > path, see man portmanager(1) > MGPMrCommandLine 0.4.1_9 error: rParseCommandLine returned errorCode 1 > Ok, so I have reviewed the code and the command line parsing is a bit odd... It separates options to commands and flags. -ui is a flag, which is not entirely obvious. Options which seem to be interpreted as commands are -sl, -slid, -s, -u, -v or category/port. Other options are treated as flags -l, -ui, --resume, etc... So, "portmanager -u -ui" seems to do what you want. I might break down and rework the parsing code eventually, as I have had other complaints about the way options are handled... robert.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1178238361.60150.15.camel>