#17477: Integrate *_select tools into port ------------------------------+--------------------------------------------- Reporter: blb@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts 1.8.0 Component: base | Version: 1.7.0 Keywords: select | Port: ------------------------------+--------------------------------------------- Comment(by perry@…): Replying to [comment:4 kngspook@…]:
Replying to [comment:2 raimue@…]:
Some additional thoughts about the syntax, I would prefer: {{{ port select [--set|--list] <group> }}}
Well, that might imply/be interpreted by a lot of people that "--set" and "--list" are optional. If we go that route, then maybe some additional logic should be in place that basically states:
* if they give only `port select something`, then treat it like a list command * if they give `port select something valid-selection`, then treat it like a set command * if they give `port select something invalid-selection`, then show an error stating as such and give them the list of valid picks.
Both suggestions seem reasonable. "--set|--list" seems more in line with the other port commands (and consistency is certainly good :)). For now, I'll implement the logic you brought up. It makes sense to me, and if users find it confusing, we can always tweak it then. Also, I'll move the code to port1.0 -- after the discussion in IRC, it seems like that is the most reasonable place to put it (factoring in the whole reality differing from ideals ;)). One additional command that I'm thinking of implementing is to show the currently selected version (the current *_select tools don't show this). I'll likely try to add this command after implementing the above suggestions. -- Ticket URL: <http://trac.macports.org/ticket/17477#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS