[csw-maintainers] [csw-users] Munin 1.3.4 in testing

[Ben Walton]

Excerpts from Philip Brown's message of Tue Jul 07 00:45:35 -0400 2009:
> > ...But they are part of the apache configuration, so it would make
> > sense to group them logically with the rest of the apache
> > configuration.
> 
> it doesnt share well. This is something meant to be potentialy shared.
> if there isnt a strong reason to keep something OUT of /opt/csw.. it
> belongs under /opt/csw

The munin package already ships files in /etc/opt/csw/munin though,
which are machine local configuration.  Why not keep things together?
If munin shipped a manifest that didn't touch /etc/ or /var on the
machine, your point would be better received on my end.  [It's still
well recieved, I just don't think it applies well to this particular
situation.]

> there is no reason to keep the read-only config as machine-local

But it's not 100% read only.  As Trygve mentioned, it may need to be
tuned to put security restrictions into it, etc.

> >  Personally though, I like the way debian does this.
> 
> Hnmmm. not sure i like that way we can come up with something better
> perhaps :)

It would be nice to have this extended into something like their
a2enmod/a2ensite setup (for modules and vhosts).  Placing the files in
$apacheconf/addons-available and then symlinking into
$apacheconf/addons-enabled would be nicer, I think.  If it were
decided that all shipped apache config snippets should live with the
rest of the apache config, this would get my vote.

Maybe one the following ground rules could be used?

1. Install all apache config files in the directory apache puts its
   own configuration in (most likely a sub-directory, for clarity).
2. If the package ships other machine local config, put the file with
   those, otherwise, somewhere in /opt/csw/etc?

Thanks
-Ben
-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.