Date: Mon, 30 Jul 2018 22:23:27 +0200 From: Guido Falsi <mad@madpilot.net> To: Jan Beich <jbeich@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: setting port options for multiple ports Message-ID: <407e5007-ab20-5561-e246-058790bedbba@madpilot.net> In-Reply-To: <wotc-sgpn-wny@FreeBSD.org> References: <CALM2mEk8bV9cLUorzh6jJ4Os_g_j=iz6pef5tuaSbxYRD%2BJQAA@mail.gmail.com> <436f5814-9775-98ff-1963-e18c2359bbd4@madpilot.net> <wotc-sgpn-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/30/18 8:48 PM, Jan Beich wrote: > 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. Oh yes, I forgot to mention that. Thanks for filling my omission! -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?407e5007-ab20-5561-e246-058790bedbba>