* Dirk Eddelbuettel <[EMAIL PROTECTED]> [2005-03-19 20:09]:
> One relatively easy way to deal with that in _user space_ is via
> dpkg-divert(8) and --local diversion:

 Just for the record, I don't call that _user_ space. That's admin area.
On the other hand it's admin area anyway to configure blosxom for
multiple user accounts. Though still dpkg-divert should be rarely used
by a system's administrator, its intention were others.

> 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.  

 Not only programmatically (what a word ;)), but also from a sane point
of view. This is going to be addressed. <nitpick>And, it's link them
_from_ where blosxom expects them. :)</nitpick>

> It's not that rapid upstream development will overwrite this

 That's not a point for a clean solution, I wonder why you bring it
up...

> -- there hasn't been any upstream work on blosxom itself in quite some
> time (as opposed to plugins etc where user still contribute, AFAIK).

 Well, there was, but you don't seem to be hanging out on the list. But
blosxom3 isn't really ready yet, unfortunately.

> Dirk, a former blosxom maintainer

 I can understand why you give up on it, with the current "strange"
setup...  It's always easier to leave the fixing to others. *sigh*

 So long,
Alfie
-- 
"Where do you want to go today?
 Somewhere, somewhere you could never take me"
                                  -- Chumbawamba, "Pass It Along"

Attachment: signature.asc
Description: Digital signature

Reply via email to