[MacPorts] #38381: RFE: pseudo-portnames `depof:` and `rdepof:` should be more granular
#38381: RFE: pseudo-portnames `depof:` and `rdepof:` should be more granular -------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Keywords: | Port: -------------------------+-------------------------------- What I mean is I want to be able to do something like `port echo lib_depof:foo` or `port echo lib_rdepof:foo` to get just the (recursive) library dependencies of port foo. This would be useful for my [https://github.com/cooljeanius/macportsscripts/blob/master/port- depcheck.sh port-depcheck.sh] script so I can have it not list build dependencies as unnecessary dependencies. -- Ticket URL: <https://trac.macports.org/ticket/38381> MacPorts <http://www.macports.org/> Ports system for OS X
#38381: RFE: pseudo-portnames `depof:` and `rdepof:` should be more granular --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by ryandesign@…): Replying to [ticket:38381 egall@…]:
I want to be able to do something like `port echo lib_depof:foo`
There's already `port deps --no-build foo` which is a shortcut for `port info --pretty --depends_lib --depends_run foo` so you could customize the `port info` invocation further. But it would be nice to have it as a pseudo-port.
or `port echo lib_rdepof:foo`
That functionality would be good to have. -- Ticket URL: <https://trac.macports.org/ticket/38381#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#38381: RFE: pseudo-portnames `depof:` and `rdepof:` should be more granular --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by jmr@…): You probably want --line rather than --pretty if you're parsing the output. -- Ticket URL: <https://trac.macports.org/ticket/38381#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#38381: RFE: pseudo-portnames `depof:` and `rdepof:` should be more granular --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by egall@…): `port info` prints full path-style dependencies when they're used, is there a way to get just the portnames when path-style dependencies are used? Preferably without too many pipes through `cut` and `tr`... (currently I'm trying `port info --line --depends_lib foo | tr \, \\n | cut -d: -f2`) -- Ticket URL: <https://trac.macports.org/ticket/38381#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#38381: RFE: pseudo-portnames `depof:` and `rdepof:` should be more granular --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by larryv@…): Replying to [comment:3 egall@…]:
`port info` prints full path-style dependencies when they're used, is there a way to get just the portnames when path-style dependencies are used? Preferably without too many pipes through `cut` and `tr`...
(currently I'm trying `port info --line --depends_lib foo | tr \, \\n | cut -d: -f2`)
There are plenty of ways. {{{ % port info --line --depends_build fish | tr ',' '\n' | awk -F ':' '{ print $NF; }' }}} -- Ticket URL: <https://trac.macports.org/ticket/38381#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#38381: RFE: pseudo-portnames `depof:` and `rdepof:` should be more granular --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by egall@…): Replying to [comment:4 larryv@…]:
Replying to [comment:3 egall@…]:
`port info` prints full path-style dependencies when they're used, is there a way to get just the portnames when path-style dependencies are used? Preferably without too many pipes through `cut` and `tr`...
(currently I'm trying `port info --line --depends_lib foo | tr \, \\n | cut -d: -f2`)
There are plenty of ways. {{{ % port info --line --depends_build fish | tr ',' '\n' | awk -F ':' '{ print $NF; }' }}}
Thanks; I guess I'll use this for now, but it'd still be a lot easier if there were a pseudo-portname that I could use instead of having to know `awk`... -- Ticket URL: <https://trac.macports.org/ticket/38381#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts