Opened 10 years ago

Closed 10 years ago

Last modified 8 years ago

#44507 closed defect (fixed)

port select usage string issue(s)

Reported by: ora.et.labora@… Owned by: neverpanic (Clemens Lang)
Priority: Low Milestone: MacPorts 2.3.5
Component: base Version: 2.3.1
Keywords: Cc: cooljeanius (Eric Gallager)
Port:

Description

The usage string of port select is not entirely correct and thus confusing:

$ port select
Error: port select [--list|--set|--show|--summary] <group> [<version>]

# ok, so a *group* argument is mandatory, right?

$ port select --summary mysql
Warning: The 'summary' command does not expect any arguments. Extra arguments will be ignored.
[..]

Obviously not. Thus, the usage string must be:

$ port select
Error: usage:
port select [--list|--show] <group> 
port select --set <group> <version>
port select --summary

My personnel taste on this is to have one action per task, i.e.

$ port select-set mysql mysql56
$ port select-list mysql
$ port select-summary
$ port select-show mysql

Change History (4)

comment:1 Changed 10 years ago by neverpanic (Clemens Lang)

Milestone: MacPorts Future
Owner: changed from macports-tickets@… to cal@…
Status: newassigned

comment:2 Changed 10 years ago by neverpanic (Clemens Lang)

Resolution: fixed
Status: assignedclosed

Thanks, r122827, in the next MacPorts release. I agree we could have separate actions, but I'm not sure the change is worth breaking the existing setup (which users are used to by now). Patches (that possibly add this as optional new variant and deprecate the old one) always welcome, though.

comment:3 Changed 10 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

comment:4 Changed 8 years ago by raimue (Rainer Müller)

Milestone: MacPorts FutureMacPorts 2.3.5
Note: See TracTickets for help on using tickets.