Re: running macports along with homebrew

2018-03-05 Thread db
On 4 Mar 2018, at 05:16, Ken Cunningham wrote: >github.setupauthor project HEAD >checksum {} Thanks, Ken. I didn't think it'd be that easy. Only caveat is that it fails the livecheck and there's no way to correlate HEAD to a date. The commit

Re: running macports along with homebrew

2018-03-05 Thread Ken Cunningham
Indeed. Db had asked how it would technically be done, eg in his personal repo. I am also on neither side in this. K Sent from my iPhone > On Mar 5, 2018, at 2:39 AM, Ryan Schmidt wrote: > >> On Mar 5, 2018, at 04:34, db wrote: >> >> I know, but I don't see how

Re: running macports along with homebrew

2018-03-05 Thread Ryan Schmidt
On Mar 5, 2018, at 04:34, db wrote: > > I know, but I don't see how HEAD is pragmatically that much different from > the devel ports that use a hash+date instead. "HEAD" is not a specific version. It will vary as developers make new commits. A user installing a port that fetches from "HEAD"

Re: running macports along with homebrew

2018-03-05 Thread db
On 5 Mar 2018, at 11:39, Ryan Schmidt wrote: > hash+date is specific, predictable, repeatable. The portfile developer tests > a specific hash+date, and when satisfied, commits it to make it available to > MacPorts users. As I said in my previous post, you can get

Installing ports from HEAD

2018-03-05 Thread Mojca Miklavec
On 5 March 2018 at 11:39, Ryan Schmidt wrote: > On Mar 5, 2018, at 04:34, db wrote: >> >> I know, but I don't see how HEAD is pragmatically that much different from >> the devel ports that use a hash+date instead. > > "HEAD" is not a specific version. It will vary as developers make new >

Re: running macports along with homebrew

2018-03-05 Thread Ryan Schmidt
On Mar 5, 2018, at 05:43, db wrote: > On 5 Mar 2018, at 11:39, Ryan Schmidt wrote: >> hash+date is specific, predictable, repeatable. The portfile developer tests >> a specific hash+date, and when satisfied, commits it to make it available to >> MacPorts users. > > As I said in my previous

Did anyone else's Perl 5.26 suddenly break?

2018-03-05 Thread Dave Horsfall
A script that I wrote and has worked fine for ages is now breaking with: Can't locate Scanner.pm in @INC (you may need to install the Scanner module) (@INC contains: /opt/local/lib/perl5/site_perl/5.26/darwin-thread-multi-2level /opt/local/lib/perl5/site_perl/5.26

Re: Did anyone else's Perl 5.26 suddenly break?

2018-03-05 Thread Ryan Schmidt
On Mar 5, 2018, at 20:06, Dave Horsfall wrote: > A script that I wrote and has worked fine for ages is now breaking with: > >Can't locate Scanner.pm in @INC (you may need to install the Scanner > module) (@INC contains: > /opt/local/lib/perl5/site_perl/5.26/darwin-thread-multi-2level >