From owner-freebsd-ports@freebsd.org  Sun Jan 10 20:51:20 2016
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9F04DA6B7D4
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Sun, 10 Jan 2016 20:51:20 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::50:5])
 by mx1.freebsd.org (Postfix) with ESMTP id 910D7134B
 for <freebsd-ports@freebsd.org>; Sun, 10 Jan 2016 20:51:20 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 8E808A6B7D3; Sun, 10 Jan 2016 20:51:20 +0000 (UTC)
Delivered-To: ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E1C6A6B7D2
 for <ports@mailman.ysv.freebsd.org>; Sun, 10 Jan 2016 20:51:20 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5676D134A
 for <ports@freebsd.org>; Sun, 10 Jan 2016 20:51:20 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.86 (FreeBSD))
 (envelope-from <lists@opsec.eu>) id 1aIMxP-000KGd-90
 for ports@freebsd.org; Sun, 10 Jan 2016 21:51:23 +0100
Date: Sun, 10 Jan 2016 21:51:23 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: ports@freebsd.org
Subject: ports, dependencies and conflicts with other ports' options ?
Message-ID: <20160110205123.GY35480@home.opsec.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jan 2016 20:51:20 -0000

Hi!

There's a PR for a new port, see

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

which has the problem that if some other port has some option
set, this will cause this new port fail on build.

So the question is: Is there any idea on how one might
document / encode this kind of CONFLICT ?

I'm pretty sure there's no mechanism in place right now,
any ideas on a mechanism that would cover this ?

-- 
pi@opsec.eu            +49 171 3101372                         4 years to go !