Yes, the scripts can be placed anywhere. Typically, you would
put them somewhere in your $PATH so that you do not have to
remember where they are but this is not actually required.
Mathias
> On 21 Jan 2015, at 22:11, Jeremy Lavergne wrote:
>
> On Wed, January 21, 2015 20:58, Murray Eisenberg
On Wed, January 21, 2015 20:58, Murray Eisenberg wrote:
> Where should one place those two scripts on one's computer?
It looks like they can both run from anywhere, making use of your $PATH to
find MacPorts.
___
macports-users mailing list
macports-use
Where should one place those two scripts on one's computer?
On Sat, 17 Jan 2015 10:30:44 -0500, Jeremy Lavergne
wrote:
> You might consider adding this to the MacPorts respository, alongside the
> Tcl version of your script:
> http://trac.macports.org/browser/contrib/port-depgraph/port-depgraph
Sure! I completely missed that that version.
I filed a Ticket #46602.
> On 17 Jan 2015, at 16:30, Jeremy Lavergne wrote:
>
> You might consider adding this to the MacPorts respository, alongside the
> Tcl version of your script:
> http://trac.macports.org/browser/contrib/port-depgraph/port-dep
You might consider adding this to the MacPorts respository, alongside the
Tcl version of your script:
http://trac.macports.org/browser/contrib/port-depgraph/port-depgraph
On Sat, January 17, 2015 10:28, Mathias Laurin wrote:
> I am into graphs these days and I wrote a short python script to
> gene
I am into graphs these days and I wrote a short python script to
generate a dot file (input for graphviz) of the dependencies of
ports. It can be fed with several ports e.g. "$(port echo
outdated)" and understands variants.
I actually find it useful so I thought I would share...
In any case it i
