[MacPorts] #33064: port new actions: active, inactive
MacPorts
noreply at macports.org
Mon Jan 30 09:32:26 PST 2012
#33064: port new actions: active, inactive
-------------------------------------+--------------------------------------
Reporter: and.damore@… | Owner: macports-tickets@…
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: base | Version: 2.0.3
Keywords: haspatch | Port: bash-completion
-------------------------------------+--------------------------------------
Changes (by ryandesign@…):
* keywords: haspatch base => haspatch
* component: ports => base
Comment:
But that's just it: the outdated action is not the same as the echo
action. "port outdated" (which is a shortcut for "port outdated outdated")
does not produce the same output as "port echo outdated".
You're suggesting we provide a shortcut for "port echo active", but it's
just as likely that I'd want to see the output of "port installed active"
instead. I don't think it makes sense to add a shortcut for one and not
the other.
Remember also that we can now use the shortest unambiguous name for a
command, so I can type "port ac" to activate a port:
{{{
$ sudo port ac vobcopy @1.2.0_0+universal
---> Computing dependencies for vobcopy
---> Deactivating vobcopy @1.2.0_1+universal
---> Activating vobcopy @1.2.0_0+universal
---> Cleaning vobcopy
}}}
With your patch, this case would no longer work; I would instead get:
{{{
$ sudo port ac vobcopy @1.2.0_0+universal
Ambiguous action "ac": could be any of {activate active}.
}}}
So for all these reasons I agree with jmr that we should not implement
this suggestion.
If we were to implement the suggestion, remember that we have a third
pseudo-port: actinact, which shows ports which have both an active and at
least one inactive version installed.
--
Ticket URL: <https://trac.macports.org/ticket/33064#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list