On 14 Apr 2017, at 01:59, Ryan Schmidt wrote:
> Sure. That's still valid. There haven't been any changes in port-depgraph
> since we moved to GitHub so there's no particular advantage to switching the
> portfile to GitHub yet.
I think the tcl script should be in base, the python script might be
> On Apr 13, 2017, at 16:38, db wrote:
>
> On 13 Apr 2017, at 17:38, Rainer Müller wrote:
>> You are effectively running it with an empty argument, which is not a valid
>> port name:
>> $ port-depgraph ""
>> That could indeed be handled more graceful. The source can be found here
>> after the
On 13 Apr 2017, at 17:38, Rainer Müller wrote:
> You are effectively running it with an empty argument, which is not a valid
> port name:
> $ port-depgraph ""
> That could indeed be handled more graceful. The source can be found here
> after the move to GitHub:
> https://github.com/macports/mac
On 2017-04-12 16:02, db wrote:
> On 11 Apr 2017, at 22:36, db wrote:
>> Without arguments shows this warning
>>
>> $ port-depgraph
>> Warning: It looks like your PortIndex file for file:///opt/local/myports may
>> be corrupt.
>> Warning: It looks like
On 11 Apr 2017, at 22:36, db wrote:
> Without arguments shows this warning
>
> $ port-depgraph
> Warning: It looks like your PortIndex file for file:///opt/local/myports may
> be corrupt.
> Warning: It looks like your PortIndex file for
> file:///opt/local/var/macpor
Without arguments shows this warning
$ port-depgraph
Warning: It looks like your PortIndex file for file:///opt/local/myports may be
corrupt.
Warning: It looks like your PortIndex file for
file:///opt/local/var/macports/sources/github.com/macports/macports-ports/ may
be corrupt.
Error
