From owner-freebsd-ports-bugs@FreeBSD.ORG  Thu Aug 21 12:29:18 2014
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
Delivered-To: freebsd-ports-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 0314BFAC
 for <freebsd-ports-bugs@FreeBSD.org>; Thu, 21 Aug 2014 12:29:18 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D18D13F82
 for <freebsd-ports-bugs@FreeBSD.org>; Thu, 21 Aug 2014 12:29:17 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7LCTHDN057848
 for <freebsd-ports-bugs@FreeBSD.org>; Thu, 21 Aug 2014 12:29:17 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 189059] [new port] devel/diffconvert maintainer-update,
 master-sites
Date: Thu, 21 Aug 2014 12:29:17 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports Tree
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: marino@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-189059-13-BoeVjLLlc2@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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Aug 2014 12:29:18 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189059

--- Comment #9 from John Marino <marino@FreeBSD.org> ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.