Date: Mon, 2 Jun 2025 21:57:02 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: Warner Losh <imp@bsdimp.com> Cc: Kyle Evans <kevans@freebsd.org>, <src-committers@freebsd.org>, <dev-commits-src-all@freebsd.org>, <dev-commits-src-main@freebsd.org>, <sjg@juniper.net> Subject: Re: git: 61d77e6c0095 - main - loader: allow for exceptions to restricted settings. Message-ID: <60026.1748926622@kaos.jnpr.net> In-Reply-To: <CANCZdfqK6PpY64gbVJ%2Bsa5UdWpLhra5=uVE8NFcKQCGc0XknSg@mail.gmail.com> References: <202506020549.5525nuDu054998@gitrepo.freebsd.org> <24533e37-2396-40ef-ba84-a5339b811527@FreeBSD.org> <CANCZdfqK6PpY64gbVJ%2Bsa5UdWpLhra5=uVE8NFcKQCGc0XknSg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh <imp@bsdimp.com> wrote: > > Long-term, we should probably work out something that can work for > > lualoader, too. We use setenv() there directly rather than adding a > > layer of indirection through the command-line parser. > = > Yea, I'd rather this be a property of the env variable than having lists= like > this anyway. And that would solve another problem I have from time to > time As in noting where it can be set? > which is needing to have an always existing env variable with a default,= but > overridable value. In these cases, you have to set that up in code, and = it's a > bit of a bother. If we do it right, we could have a three-fer: works > with lua, works > to set certain things immutable after a time and also lets us initialize= things. > Though getting the details right so that we can set these in > loader.conf, but then > not set them on the command line is the most likely use case, and I > thought for that > use case we did the right thing in lualoader. no? > = > Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?60026.1748926622>