Warner Losh <i...@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
