[MacPorts] #26007: port clean doesn't conform to the man page instructions
#26007: port clean doesn't conform to the man page instructions ---------------------------------+------------------------------------------ Reporter: paulbeard@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 1.9.1 Keywords: port clean | Port: ---------------------------------+------------------------------------------ Specifically the "all" flag: "To remove the work files, distribution files and archives, pass --all. To remove log files for certain port, pass --logs. For example: port clean --dist vim port clean --archive vim port clean --logs vim [/Users/paul]# port clean --all Can't map the URL 'file://.' to a port description file ("Could not find Portfile in /Users/paul"). Please verify that the directory and portfile syntax are correct. To use the current port, you must be in a port's directory. [/Users/paul]# port -v clean all ---> Cleaning 2Pong ---> Removing build directory for 2Pong ---> Cleaning 3proxy ---> Removing build directory for 3proxy ---> Cleaning 4th ---> Removing build directory for 4th -- Ticket URL: <http://trac.macports.org/ticket/26007> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26007: port clean doesn't conform to the man page instructions ---------------------------------+------------------------------------------ Reporter: paulbeard@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 1.9.1 Keywords: port clean | Port: ---------------------------------+------------------------------------------ Comment(by blb@…): {{{--all}}} and {{{all}}} are actually different, and you can use them both as in {{{port clean --all all}}} as {{{--all}}} applies to whichever port(s) is given to clean and {{{all}}} is the actual port to clean. The examples in the man page could also include {{{port clean --all vim}}}, would that help make it clearer? -- Ticket URL: <http://trac.macports.org/ticket/26007#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26007: port clean doesn't conform to the man page instructions ---------------------------------+------------------------------------------ Reporter: paulbeard@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 1.9.1 Keywords: port clean | Port: ---------------------------------+------------------------------------------ Comment(by paulbeard@…): Replying to [comment:1 blb@…]:
{{{--all}}} and {{{all}}} are actually different, and you can use them both as in {{{port clean --all all}}} as {{{--all}}} applies to whichever port(s) is given to clean and {{{all}}} is the actual port to clean.
The examples in the man page could also include {{{port clean --all vim}}}, would that help make it clearer?
Why not just make {{{port clean all}}} work as expected/advertised? That works but why would anyone do that? -- Ticket URL: <http://trac.macports.org/ticket/26007#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26007: port clean doesn't conform to the man page instructions ----------------------------------+----------------------------------------- Reporter: paulbeard@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 1.9.1 Resolution: invalid | Keywords: port clean Port: | ----------------------------------+----------------------------------------- Changes (by jmr@…): * status: new => closed * resolution: => invalid Comment: Working as documented. -- Ticket URL: <http://trac.macports.org/ticket/26007#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26007: port clean doesn't conform to the man page instructions ----------------------------------+----------------------------------------- Reporter: paulbeard@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 1.9.1 Resolution: invalid | Keywords: port clean Port: | ----------------------------------+----------------------------------------- Comment(by paulbeard@…): "port clean --all all as --all applies to whichever port(s) is given to clean and all is the actual port to clean." There is no mention of {{{port clean all}} in the manual. {{{[/Users/paul]:: man port | col -b | grep "clean all" (paul@gee5.paulbeard.org)-(08:14 AM / Mon Aug 09) [/Users/paul]:: }}} -- Ticket URL: <http://trac.macports.org/ticket/26007#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26007: port clean doesn't conform to the man page instructions ----------------------------------+----------------------------------------- Reporter: paulbeard@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 1.9.1 Resolution: invalid | Keywords: port clean Port: | ----------------------------------+----------------------------------------- Comment(by sewebster@…): "all" has nothing in particular to do with port clean. It is just a list of all ports. So if you want to clean all ports, you "port clean all", if you want to install all ports, you "port install all" etc. The "all" pseudo-portname is explained very close to the beginning of the man page. "port clean --all all" is an ok way of cleaning almost everything, but probably shouldn't be included in the documentation, because the list of all ports is very very long, and most people likely don't need to do this. -- Ticket URL: <http://trac.macports.org/ticket/26007#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts