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
t-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
>> generate a dot file (input for graphviz) of the dependencies of ports. It
>> can be fed with several ports e.g. &qu
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
> Wouldn't the stopping of function export from MacPorts' bash be a big
> restriction on bash use. For example, I want to be able to type "mvim", with
> or without parameters, to open a MacVim window. At present, I get the error:
> "/bin/sh: line 8: `BASH_FUNC_usenosql%%': not a valid identifier"
Dear MacPorts users,
Some ports like py-ipython and py-cython do not set
`python.default_version`. The result is that `port install py-ipython`
pulls py24-ipython. So (1) should this be reported as a bug (the patch
is trivial in any case)? (2) I could not find how to tell port that
`py-ipython
