Bug#362864: Bug#411152: aptitude: should reject *all* extra cmd line arguments
On Sat, Mar 10, 2007 at 05:55:36PM -0800, Daniel Burrows wrote:
> On Sat, Mar 10, 2007 at 06:53:59PM -0500, Justin Pryzby <justinpryzby@users.sourceforge.net> was heard to say:
> > On Sat, Mar 10, 2007 at 11:00:26AM -0800, Daniel Burrows wrote:
> > > On Fri, Feb 16, 2007 at 11:22:36AM -0500, Justin Pryzby <pryzbyj@justinpryzby.com> was heard to say:
> > > > $ time aptitude update asdf
> > > > E: The update command takes no arguments
> > > >
> > > > While dist-upgrade notices extra arguments, but they don't seem to have
> > > > any effect on behavior or exit status. But upgrade asdf doesn't seem to
> > > > even notice them.
> > > >
> > > > See also apt #362864.
> > >
> > > darcs head should now complain loudly if a command that doesn't use
> > > its arguments is given arguments. Note, though, that dist-upgrade does
> > > in fact read its extra arguments (you can toss in extra commands to be
> > > included in the upgrade).
> > Great! Do you mean extra packages?
>
> Any command that's legal for "install". e.g.,
>
> aptitude dist-upgrade foo blah/testing bar- x_
Okay, thanks. I've already suggested that apt work likewise (for the
"install" syntaxes that it supports): #362864.
Since aptitude acts this way and at present apt-get dist-upgrade
silently ignores further arguments, that still makes sense.
Justin
Reply to: