cjs@portal.ca (Curt Sampson) writes:
>On the other hand, httpd config files are pretty site-specific
>documents in many ways, and I'd be hesitant to make the next sighup
>run the code just because it's installed; what if the person
>installed it in order to add it to the test web server on the
>machine, rather than the production one?

It seems to me that the right solution is to change some _sample_
configuration files.  We already have a policy not to randomly change
system configuration files.  E.g. "make build" and sysinst don't clobber
/etc/.

Hmm, when a package that depends on another package changes files registered
with that other package, doesn't that cause the deinstallation of the
depended-on package to fail?  This get's ugly several packages do that
for a depended-on package.

-- 
Christoph Badura
Verlag O'Reilly