On Fri, Jan 28, 2022 at 06:21:40PM -0500, Wietse Venema <wie...@porcupine.org> wrote:
> Viktor Dukhovni: > > > On 28 Jan 2022, at 4:46 pm, raf <post...@raf.org> wrote: > > > > > >> Well for things like "import_environment" or "proxy_read_maps", ... > > >> you really do want to know just the additions to the built-in > > >> defaults. > > > > > > Good point. > > > > Of course a cheap cop out to handle just these special cases is > > to include an extension variable dereference in the default > > value: > > > > import_environment = ... default settings ... $site_import_environment > > > > Then the user can just assign a non-empty value to $site_import_environment. > > Ditto for "proxy_read_maps". Perhaps this would be enough, if we augment > > the variables for which this is most likely to be useful... > > Let's not do special cases, that just makes Postfix more confusing. > > > Of course "+=" would be much more general, and perhaps not too painful > > to implement... > > To raj's concern about this making main.cf harder to understand, > I'd like to add that postconf would display only the final value: > > main.cf: > # Assuming that foo has a default value of 'whatever' > foo += bar > foo += baz > > Command and output: > $ postconf foo > whatever bar baz That's fine. It's great for this mailing list. And people looking at their own actual main.cf files are probably very familiar them and know whether or not parts of a particular parameter are spread out around the file. > People who must use "grep" would have to do some extra work. Luckily, it would just be grepping the output of postconf instead. :-) > Wietse cheers, raf
