Re: Not much reason to have */R-cran-* ports

2018-03-20 Thread Eugene Grosbein
21.03.2018 3:32, Yuri wrote: > On 03/20/18 11:20, Eugene Grosbein wrote: >> It is a bit funny you are bothered on 250 R-cran-* ports when we have 1908 >> p5-* ports, >> 964 py-* ports, 600 rubygem-* ports and 280 hs-* ports in the single >> ports/devel category. >> >> Are you planning to ban

Committer needed for new port (net/nuster)

2018-03-20 Thread Felix Hanley
Hi all, There is a new port (net/nuster) awaiting approval at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225721 If there are no suggestions could someone commit it please. -felix ___ freebsd-ports@freebsd.org mailing list

Re: Not much reason to have */R-cran-* ports

2018-03-20 Thread Rainer Hurling
Am 20.03.2018 um 21:32 schrieb Yuri: > On 03/20/18 11:20, Eugene Grosbein wrote: >> It is a bit funny you are bothered on 250 R-cran-* ports when we have >> 1908 p5-* ports, >> 964 py-* ports, 600 rubygem-* ports and 280 hs-* ports in the single >> ports/devel category. >> >> Are you planning to

Re: Not much reason to have */R-cran-* ports

2018-03-20 Thread Yuri
On 03/20/18 11:20, Eugene Grosbein wrote: It is a bit funny you are bothered on 250 R-cran-* ports when we have 1908 p5-* ports, 964 py-* ports, 600 rubygem-* ports and 280 hs-* ports in the single ports/devel category. Are you planning to ban and remove p5 ports too? Most of them should be

Re: Not much reason to have */R-cran-* ports

2018-03-20 Thread Kurt Jaeger
Hello, Eugene wrote: > It is a bit funny you are bothered on 250 R-cran-* ports when we > have 1908 p5-* ports, 964 py-* ports, 600 rubygem-* ports and > 280 hs-* ports in the single ports/devel category. This is an important point. Every toolchain does its own dependency tracking etc. So maybe

Re: Not much reason to have */R-cran-* ports

2018-03-20 Thread Eugene Grosbein
21.03.2018 0:01, Yuri wrote: > FreeBSD should consider banning and removing them, in the same way as Go > libraries are banned. Inability to download fixed and known working version and surely not hijacked distfile of Go library is really bad. That is, one of strongest sides of FreeBSD Ports

Not much reason to have */R-cran-* ports

2018-03-20 Thread Yuri
There are more than 250 R-cran-* ports. They are R packages. The thing is that R has its own, very capable package manager which can find packages, download them, check hash, build, find upgrades. Every R-cran-* port can be easily installed through R itself, so there is really no need for

Re: remove the python limition of qt5-webkit (if possible)

2018-03-20 Thread Mathieu Arnold
On Wed, Mar 14, 2018 at 12:03:13AM +0100, Walter Schwarzenfeld wrote: > If try to install qt5-webkit from a dependend port I got: > > qt5-webkit-5.212.0.a2_5 needs Python 2.7 at most, but 3.6 was specified What environment do you have that creates this error message? I do not see how it can

Re: What is the status of the ical calendar program?

2018-03-20 Thread Bob Willcox
On Tue, Mar 20, 2018 at 11:50:44PM +1100, Kubilay Kocak wrote: > On 20/03/2018 11:39 pm, Bob Willcox wrote: > > Attempting to build ical on any of my 12.0-CURRENT systems results in this > > error: > > > > fatal error: too many errors emitted, stopping now [-ferror-limit=] > > 3836 warnings and

Re: What is the status of the ical calendar program?

2018-03-20 Thread Kubilay Kocak
On 20/03/2018 11:39 pm, Bob Willcox wrote: > Attempting to build ical on any of my 12.0-CURRENT systems results in this > error: > > fatal error: too many errors emitted, stopping now [-ferror-limit=] > 3836 warnings and 20 errors generated. > *** [main.o] Error code 1 > > make[1]: stopped in

What is the status of the ical calendar program?

2018-03-20 Thread Bob Willcox
Attempting to build ical on any of my 12.0-CURRENT systems results in this error: fatal error: too many errors emitted, stopping now [-ferror-limit=] 3836 warnings and 20 errors generated. *** [main.o] Error code 1 make[1]: stopped in /usr/ports/deskutils/ical/work/ical-2.2 1 error make[1]:

Re: how to get autoconf to run

2018-03-20 Thread Mathieu Arnold
On Mon, Mar 19, 2018 at 08:20:17PM +0100, Kurt Jaeger wrote: > Hi! > > > Hate to return so soon, but what is required in Makefile to get > > autoconf to do its thing? USE_AUTOTOOLS have been retired, I forgot to remove them from the Porter's Handbook, it's now done. > Look at

Re: "converters/php72-mbstring" build failure

2018-03-20 Thread Herbert J. Skuhra
On Tue, Mar 20, 2018 at 10:20:38AM +, Carmel NY wrote: > On Mon, 19 Mar 2018 21:42:41 +1100, Kubilay Kocak stated: > > >On 19/03/2018 9:33 pm, Kubilay Kocak wrote: > >> On 19/03/2018 9:22 pm, Carmel NY wrote: > >>> FreeBSD-11.1-RELEASE-p8 > >>> > >>> I am attempting to update the

Re: "converters/php72-mbstring" build failure

2018-03-20 Thread Carmel NY
On Mon, 19 Mar 2018 21:42:41 +1100, Kubilay Kocak stated: >On 19/03/2018 9:33 pm, Kubilay Kocak wrote: >> On 19/03/2018 9:22 pm, Carmel NY wrote: >>> FreeBSD-11.1-RELEASE-p8 >>> >>> I am attempting to update the "converters/php72-mbstring" port. The older >>> version build fine. The newest

Re: committer needed for new port sysutils/tmux23

2018-03-20 Thread Miroslav Lachman
Matthias Andree wrote on 2018/03/20 10:44: yuri@ has committed this, thanks. Thank you! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: committer needed for new port sysutils/tmux23

2018-03-20 Thread Matthias Andree
yuri@ has committed this, thanks. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports you maintain which are out of date

2018-03-20 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated,