Date: Thu, 21 Aug 2014 13:33:48 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 189059] [new port] devel/diffconvert maintainer-update, master-sites Message-ID: <bug-189059-13-QR34keDFAh@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-189059-13@https.bugs.freebsd.org/bugzilla/> References: <bug-189059-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189059 --- Comment #10 from C Hutchinson <portmaster@bsdforge.com> --- (In reply to John Marino from comment #9) > I don't think having a new port that doesn't work on FreeBSD 10 or later is > going to fly. It's one thing if it was an older existing port that stopped > building (and we had plenty of those) but I consider those > "grandfathered-in". > > Even that status is basically temporary. > > My interpretation that for general usage new ports, building with base clang > is a requirement. Sure. I guess that probably makes sense. I'm putting together an 11 box, as I write this. I need [recent] clang, if I'm going to move forward with any of these ports. I've also been anxious to put redports on a dev box, as well. To help expedite development. Thanks, John, for all your hard work. --Chris -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-189059-13-QR34keDFAh>