Thomas Goirand <z...@debian.org> writes: > On 05/11/2012 05:07 PM, Gergely Nagy wrote: >> I'll turn this around: how do you handle cases where the defaults of >> packages like apt, exim or syslogd change? Where the defaults are >> embedded in the executable. >> > The thing is, if you put the default in a file, it's because you > expect these to change, at least more often than things that > are compiled-in. Otherwise, what's the point in having stuff > stored in a file that can be edited? Why not just do a .h with > the values you need?
The advantage of having the defaults in a file is that it makes it much easier to inspect them. A .h file would typically not be installed, so it wouldn't be readily available. In addition to that, it is much less expressive. The nice thing about storing the default values in the same format used by the configuration file is that if you find a default that you'd like to change, you immediately know what to put in the configuration file in order to change it. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87k40hh502....@vostro.rath.org
