Re: Ports with default modeline & lots of mixed tabs with spaces

2018-02-28 Thread Ryan Schmidt
On Feb 28, 2018, at 02:42, Mojca Miklavec wrote: > I sometimes stumble across ports which contain our default modeline > (claiming the Portfile should not use tabs) and then a weird mixture > of tabs and spaces all over the place. > > When there is no maintainer, I would always fix such a port.

Re: Java port maintainers: What should be installed on the buildbot workers?

2018-02-28 Thread Ryan Schmidt
On Feb 26, 2018, at 23:55, Aaron Madlon-Kay wrote: >> Thanks, you've cleared up another misconception I had. I had read that Java >> 7 installations were being automatically upgraded to Java 8, so I thought >> there was no point to trying to install Java 7. > > The system-default Java will

Re: Java port maintainers: What should be installed on the buildbot workers?

2018-02-28 Thread Aaron Madlon-Kay
> You had mentioned Java 9 introducing changes that were not backward > compatible. Does that only apply to the JDK, and not the JRE? Should the Java > 9 JRE be able to run stuff made with any earlier Java version? Compared to previous updates, Java 9 breaks a lot of things and no, a lot of

Re: Java port maintainers: What should be installed on the buildbot workers?

2018-02-28 Thread Ryan Schmidt
On Feb 28, 2018, at 08:08, Aaron Madlon-Kay wrote: >> Ok. Then my plan is to install the Apple Java 6 JDK and the Oracle Java 7, 8 >> and maybe 9 JDK, and the Oracle Java 8 JRE. Does that cover all the bases >> for now? > > The JDKs will install the JRE automatically, and since I don’t think

Re: Java port maintainers: What should be installed on the buildbot workers?

2018-02-28 Thread Aaron Madlon-Kay
> Ok. Then my plan is to install the Apple Java 6 JDK and the Oracle Java 7, 8 > and maybe 9 JDK, and the Oracle Java 8 JRE. Does that cover all the bases for > now? The JDKs will install the JRE automatically, and since I don’t think it ever downgrades, you will end up with the Java 9 JRE

Re: [macports-ports] branch master updated: cpan2port: fetch from github, use perl5.26

2018-02-28 Thread Mojca Miklavec
On 28 February 2018 at 16:23, Ryan Schmidt wrote: > On Feb 28, 2018, at 08:13, Mojca Miklavec wrote: > >> +set git_shasum 4207b22 >> +set git_date20180228 >> + >> +github.setupmacports macports-contrib ${git_shasum} > > I'd like to disco

Ports with default modeline & lots of mixed tabs with spaces

2018-02-28 Thread Mojca Miklavec
Hi, I sometimes stumble across ports which contain our default modeline (claiming the Portfile should not use tabs) and then a weird mixture of tabs and spaces all over the place. When there is no maintainer, I would always fix such a port. I once did it for a maintained port as well, just to

Re: [macports-ports] branch master updated: cpan2port: fetch from github, use perl5.26

2018-02-28 Thread Mojca Miklavec
Fixes committed, thanks. On 28 February 2018 at 16:43, Mojca Miklavec wrote: > On 28 February 2018 at 16:23, Ryan Schmidt wrote: >> On Feb 28, 2018, at 08:13, Mojca Miklavec wrote: >> >>> -# TODO: check the latest svn revision of the file >>> +# TODO: check the latest revision of the file >>>

Re: [macports-ports] branch master updated: cpan2port: fetch from github, use perl5.26

2018-02-28 Thread Ryan Schmidt
On Feb 28, 2018, at 09:43, Mojca Miklavec wrote: > On 28 February 2018 at 16:23, Ryan Schmidt wrote: >> On Feb 28, 2018, at 08:13, Mojca Miklavec wrote: >> It's pretty crappy that we have to fetch the entire contrib repository just >> to get one of its subdirectories. I guess contrib is still

Re: #55884: mandoc @1.14.3: not using the right compiler

2018-02-28 Thread Ryan Schmidt
On Feb 28, 2018, at 01:52, Jan Stary wrote: >> I had my MacPorts configured to error out if `cc` is used >> using the method described at UsingTheRightCompiler#testing. > > Why would you do that? To detect ports that do not use a specific compiler. MacPorts policy is that all ports shall use

Re: #55884: mandoc @1.14.3: not using the right compiler

2018-02-28 Thread Rainer Müller
On 2018-02-28 08:52, Jan Stary wrote: > The ticket is closed, so I will continue here. > >> Actually it's not specific to the universal variant. Rather, the problem >> is that the port is not UsingTheRightCompiler. > > mandoc's ./configure sets CC to whatever make(1) thinks CC is: > CC=`printf

Re: LibreSSL and OpenSSL and *SSL

2018-02-28 Thread Jan Stary
> On Feb 16 20:15:04, notificati...@github.com wrote: > > OpenSSL was once undersupported because they didn't have funds > > to have full time staff doing development and maintenance. > > That ended a long time ago after Heartbleed. > > The project is now fully funded and has excellent people