Integrating local changes

[shields@crosslink.net (Michael Shields)]

I'm looking to use Debian as a base for several servers and turnkey
systems.  dpkg seems very nice, far nicer than the "Slackware plus a lot
of work" method I'm trying to kill.  And I'd be able to maintain a few
missing packages, like nn, on company time (I don't log in much at home
these days).

However, I need ways to (a) maintain configuration files, (b) replace
Debian packages with local packages when necessary, and (c) add local
packages.

(a) How would dpkg react when a package contains configuration files for
    other package(s)?  It would be nice if I could create a new server
    just by installing a stack of Debian packages and a locally
    generated package consisting of configuration files.

(b) Is there a way to create, say, an `emacs-local' package that
    conflicts with `emacs'?  Could I make `emacs' a virtual package?  Or
    should I just keep calling it `emacs' and use a different version?
    (Emacs is just an example; more likely I'd be replacing /bin/login
    or inetd or other system software.)

(c) I can create a local package (so as not to have files on the system
    not under dpkg control), but what is a clean way to add it to the
    list of available packages?
-- 
Shields, CrossLink.