From owner-freebsd-ports@freebsd.org  Mon Jul 30 18:48:09 2018
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7DB21105E2C5
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Mon, 30 Jul 2018 18:48:09 +0000 (UTC)
 (envelope-from jbeich@freebsd.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "freefall.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 36ECF7F8EC;
 Mon, 30 Jul 2018 18:48:09 +0000 (UTC)
 (envelope-from jbeich@freebsd.org)
Received: by freefall.freebsd.org (Postfix, from userid 1354)
 id 307A21E509; Mon, 30 Jul 2018 18:48:09 +0000 (UTC)
From: Jan Beich <jbeich@FreeBSD.org>
To: Guido Falsi <mad@madpilot.net>
Cc: freebsd-ports@freebsd.org
Subject: Re: setting port options for multiple ports
References: <CALM2mEk8bV9cLUorzh6jJ4Os_g_j=iz6pef5tuaSbxYRD+JQAA@mail.gmail.com>
 <436f5814-9775-98ff-1963-e18c2359bbd4@madpilot.net>
Date: Mon, 30 Jul 2018 20:48:04 +0200
In-Reply-To: <436f5814-9775-98ff-1963-e18c2359bbd4@madpilot.net> (Guido
 Falsi's message of "Mon, 30 Jul 2018 20:12:03 +0200")
Message-ID: <wotc-sgpn-wny@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.27
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: Mon, 30 Jul 2018 18:48:09 -0000

Guido Falsi <mad@madpilot.net> writes:

> On 7/30/18 1:02 PM, blubee blubeeme wrote:
>
>> I am working on a port that requires many other ports to be built with
>> specific options selected.
>> 
>> Is there any way to have a port enables options in it's dependencies?
>> 
>
> There is no way to do exactly what you are asking for, but the
> "traditional" solution is to create a slave port forcing the options you
> require and naming it accordingly.
>
> This could also be done with flavors today, but keep in mind that adding
> flavors would require approval from both the maintainer and portmgr.

Except anything else that depends on unslaved/unflavored port is likely
to cause a conflict... until variable dependencies come into play.

https://lists.freebsd.org/pipermail/freebsd-ports/2017-September/110332.html