One relatively easy way to deal with that in _user space_ is via dpkg-divert(8) and --local diversion:
[EMAIL PROTECTED]:~> dpkg -L blosxom | grep -B1 "locally" /usr/share/blosxom/timezone locally diverted to: /usr/share/blosxom/timezone.distrib -- /var/www/blosxom/flavours/content_type.html locally diverted to: /var/www/blosxom/flavours/content_type.html.distrib -- /var/www/blosxom/flavours/date.html locally diverted to: /var/www/blosxom/flavours/date.html.distrib -- /var/www/blosxom/flavours/foot.html locally diverted to: /var/www/blosxom/flavours/foot.html.distrib -- /var/www/blosxom/flavours/head.html locally diverted to: /var/www/blosxom/flavours/head.html.distrib -- /var/www/blosxom/flavours/story.html locally diverted to: /var/www/blosxom/flavours/story.html.distrib -- /etc/blosxom/blosxom.conf locally diverted to: /etc/blosxom/blosxom.conf.distrib [EMAIL PROTECTED]:~> Programmatically, and from the _package point of view_, the obvious solution is to make these conffiles in /etc and link them back to where blosxom expect them --- or patch blosxom like we did with the Debian patch for /etc/blosxom/blosxom.conf. It's not that rapid upstream development will overwrite this -- there hasn't been any upstream work on blosxom itself in quite some time (as opposed to plugins etc where user still contribute, AFAIK). Dirk, a former blosxom maintainer -- Better to have an approximate answer to the right question than a precise answer to the wrong question. -- John Tukey as quoted by John Chambers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
