From owner-freebsd-ports@freebsd.org Tue Sep 26 23:25:29 2017 Return-Path: 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 57DF8E255D4 for ; Tue, 26 Sep 2017 23:25:29 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (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 3023D7FBC8 for ; Tue, 26 Sep 2017 23:25:28 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v8QNQ8e1075765 for ; Tue, 26 Sep 2017 16:26:14 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <64b78d72-db31-7c4b-c7de-ba5a3ee6a196@FreeBSD.org> References: , <64b78d72-db31-7c4b-c7de-ba5a3ee6a196@FreeBSD.org> From: "Chris H" Subject: Re: [HEADUP] FLAVORS landing. Date: Tue, 26 Sep 2017 16:26:14 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <5bc1eb33e65e50c8cd73cce34f225402@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2017 23:25:29 -0000 On Tue, 26 Sep 2017 16:10:59 +0200 Mathieu Arnold wrote > Le 26/09/2017 à 16:05, Mathieu Arnold a écrit : > > Hi, > > > > **Do not commit FLAVORS to any ports, a hook will prevent it, that being > > said, do try it and test what can be done.** > > > > To test this feature in poudriere, you need > > poudriere-devel-3.1.99.20170621 or later. > > > > This has been a long awaiting feature, most of the work has been done by > > bapt, bdrewery and antoine, I am just the one actually doing the > > announce and commit and all. > > > > All this information, and more to come are in the first link to our wiki > > in the bottom block. A roadmap is in the second link. > > Of course, I forgot those two links. > https://wiki.freebsd.org/Ports/FlavorsMigration > https://wiki.freebsd.org/Ports/FlavorsAndSubPackages > > > To define a different flavors in a port, before any include, set: > > > > FLAVORS=  flavor1 flavor2 [...] > > > > The first flavor in the list will be the default. > > > > You can then check for flavors after includ'ing bsd.port.options.mk with: > > > > .if ${FLAVOR} == flavor2 > > [change some stuff] > > .endif > > > > To build flavor2, simply run: > > > > make FLAVOR=flavor2 > > > > To depend on a specific flavor, write @ at the end of the depend > > string, for example, to depend on flavor "foo": > > > > RUN_DEPENDS=    something:origin@foo > > > >From a USER perspective, this is an OPTION, correct? IOW I would have to specifically ask for it. I'm just hoping that it's early enough to ensure that FALVOR(S) are an OPTION not an IMPOSITION. I would like to suggest that one has to ask for it, before they can have it. For example; something like one the following in make.conf(5): USE_FLAVORS FLAVORS_ENABLE HAS_FLAVORS and it would NOT be a yes/no | true/false -- it is ALWAYS off, and must be asked for before permitted/enabled. Make no mistake; I love the flexibility that this [flavors] attempts to provide. I'm just suggesting this to help prevent (unwelcomed) surprises. :-) Thanks! --Chris > -- > Mathieu Arnold