sean finney wrote: > currently, there's a file /etc/sugarplum/apache.conf that has the > rewrite rules, including the location of /sugarplum. if i were to do > one of the above suggestions, what's the best way to handle this file? > would it still be as a conffile, even though every time the package > were upgraded it would invoke the conffile handling stuff? i've heard > a bit about loading configuration files from templates via debconf, but > haven't ever done so myself. would that be an acceptable way to do so? > and if so, anyone have an example i can use as reference?
It cannot be a conffile. Read Debian policy, section 11.7.3. You should avoid use of templates when at all possible, as it justs adds complexity that the admin has to learn to deal with. It's almost always[1] possible to just make your debconf config script parse the current settings out of the config file, and make the postinst modify the config file to put in new settings. For examples, see debconf-devel(8), section "Config file handling". -- see shy jo [1] at least
msg08583/pgp00000.pgp
Description: PGP signature
