Re: port-depgraph warning

2017-04-13 Thread Ryan Schmidt
> 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.

Re: port-depgraph warning

2017-04-13 Thread db
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: >

Re: port-depgraph warning

2017-04-13 Thread Rainer Müller
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 your PortIndex file for

Re: notes repeatedly showing in port session

2017-04-13 Thread db
On 12 Apr 2017, at 16:21, Ryan Schmidt wrote: > If you want to get this fix right now, before the next version of MacPorts is > released, the official way would be to check out the master of the repository > and build the whole thing from source. Oh well…from what I

Re: speex vs speex-devel

2017-04-13 Thread Mihai Moldovan
On 04/01/2017 06:13 AM, Ryan Schmidt wrote: > Since it looks like speex has been superseded by opus, I guess there won't be > any further major development on speex, so I agree having -devel ports isn't > useful anymore. Well, probably not, but speex is/was notorious for releasing rcs and betas