Remove utop port -- let opam handle it

2017-03-04 Thread Kenneth R Westerback
utop is the enhanced command line for ocaml. It is used to develop ocaml programs and maintaining a port is both effortful and likely to be little used once people encounter opam, where it is actively maintained with all of its dependencies and the many nifty libraries ocaml programmers might want

Remove audio/gogo?

2017-03-04 Thread Frederic Cambus
Hi ports@, The version we have in ports is from 2000, gogo is dead upstream, and this is an i386 only port. Nothing depends on it. Checking lame ChangeLog, it appears that at least some of those i386 optimizations have been merged. Comments? OK to remove it?

Re: Nuke some Ocaml ports

2017-03-04 Thread Kenneth R Westerback
On 02/28, Edd Barrett wrote: > On Mon, Feb 27, 2017 at 10:31:21PM +0100, Christopher Zimmermann wrote: > > On 2017-02-27 Daniel Dickman wrote: > > > > > > > > devel/utop > > > > > > please no. > > > > I acknowlegde this is a very useful tool for the OCaml developer, but > > it also has heavy

Re: Update net/syncthing to 0.14.23

2017-03-04 Thread Edd Barrett
On Thu, Mar 02, 2017 at 07:51:50PM -0500, trondd wrote: > Straight-forward update to get synthing to the latest release. I've been > running this for a couple of days (and .22 for a while before this), Ran > it by $MAINTAINER who said to bring it to ports@. I'm happy to commit this, if I can get

Re: [wip] Firefox 52.0rc1

2017-03-04 Thread Landry Breuil
On Wed, Mar 01, 2017 at 12:11:26PM +0100, Landry Breuil wrote: > On Wed, Feb 15, 2017 at 08:55:01AM +0100, Landry Breuil wrote: > > Yo, > > > > i realized i missed the every-six-weeks email for 51, so here's one for > > 52, which i dunno will make the cut for 6.1 - would be nice as it's an > > ESR

Re: Ports with hardcoded "gcc", "g++"

2017-03-04 Thread Christian Weisgerber
Updated list, 2017-03-04: devel/boost devel/jdk/1.7 emulators/virtualjaguar graphics/ipe lang/nim misc/rocrail net/pidgin productivity/wyrd x11/p5-Wx -- Christian "naddy" Weisgerber na...@mips.inka.de

Re: possible chromium regression on -current (caused by llvm)

2017-03-04 Thread Stuart Henderson
On 2017/03/03 16:01, Robert Nagy wrote: > The issue is caused by the llvm update most probably, > reverting back to llvm-3.9.1p0 fixes the issue, so it's either the > update or a commit after that. > > http://nerd.hu/chromium-56.0.2924.87p0.tgz for amd64 using llvm-3.9.1p0 SoundCloud fails playba