Previously Martin Bialasinski wrote: > dpkg should assume "no" (this has to be implemented somehow). The > configfiles are generated (or copied from a central repository > anyways). > > At the university, I use the following scheme to keep a bunch of > Windows 3.1 boxes updated: [.. snip snip..] There are many ways to do this. I once perl wrappers around rdist once to keep a couple of labrooms up-to-date, with some autogenerated stuff. > So for debian, this would mean: after installation, it would call a > script update-config, which will fetch the config files for this > specific box. `it' being something the administrator himself (herself? do female UNIX admins exist?) makes. Adding a --never-replace-configfile option for dpkg should do the trick. Wichert. -- ============================================================================== This combination of bytes forms a message written to you by Wichert Akkerman. E-Mail: wakkerma@cs.leidenuniv.nl WWW: http://www.wi.leidenuniv.nl/~wichert/
Attachment:
pgp1BfZObFDuT.pgp
Description: PGP signature