[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: any consideration to creating a default template rc.conf.local?

> the situation is basically the same for rc.conf.local and rc.local.
> when you use those consistently, you can treat rc and rc.conf like 
> binaries on upgrades and simply overwrite them, which is good.
> thus we either should not provide these files at all by default, or 
> no-op templates, where everything is commented out etc.


The real truth here is that if you provide a default rc.conf.local, it
will be necessary to let it source an hypothetical rc.conf.local.local
file, so that people can be sure that rc.conf.local can be upgraded