Date: Sun, 05 Jul 2015 21:03:59 +0100 From: Bruce Simpson <bms@fastmail.net> To: John-Mark Gurney <jmg@funkthat.com> Cc: src-committers <src-committers@freebsd.org>, svn-src-all@freebsd.org, Ian Lepore <ian@freebsd.org>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org> Subject: Re: svn commit: r285160 - head/sys/conf Message-ID: <55998DAF.2000609@fastmail.net> In-Reply-To: <CAPQ4ffsQK1gZQ6Gs8pLMB7n8mghOG-HtHrYBH6zLYtYdKbXo_w@mail.gmail.com> References: <201507051415.t65EFxWd044357@repo.freebsd.org> <20150705194954.GA8523@funkthat.com> <CAPQ4ffsQK1gZQ6Gs8pLMB7n8mghOG-HtHrYBH6zLYtYdKbXo_w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/07/15 20:53, Oliver Pinter wrote: >>> Log: >>> Ensure all the required files get built when you include the IPSEC >>> option. +1. IETF position these days is that IPSEC should be a "standard feature". Key management is a separate issue, and support for newer ciphers like ChaCha20 (see NaCL by Daniel Bernstein et al) and authenticated encryption schemes please. >> Umm.. This looks more like that IPSEC should require that the crypto >> device be specified instead of fixing it this way... +1. Expressing static dependencies at the granularity of "file" rather than "module" or "subsystem" is a PITA, and leads to having to depth-first enumerate the deps like this, introducing clutter. > Is there any way to specify implication rules to config? > Ergo if I specify IPSEC without device crypto, then it's auto enable/include. > Similar to linux's Kconfig framework.. +1. I know this can be done at "module" granularity, but I have always found the "options" and "files" syntax somewhat arcane. I almost always copy-paste-edit existing stanzas.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55998DAF.2000609>