On Mon, May 09, 2005 at 01:11:18PM +0200, Tore Anderson wrote: > * Marc Haber > > torrus is an example of the other kind. I remember not liking the > > cricket packaging at all, and mrtg is probably not a very good > > example. > > I'm not so sure if I like the torrus packaging, with one binary > package per httpd.
It is, however, working fine. Torrus only supports apache and apache2 upstream, so things are much easier though. > 19 packages is providing "httpd" as far as I can > see, and I'd like Munin to work with all of them, but having one binary > package per httpd doesn't seem like a viable option. How about having a binary package for the major httpds? People using an exotic httpd surely have the knowledge of hacking their own configuration. > Using /var/www/munin is quite nice in that case, as it'll work with > any web server without any extra configuration needed. Yes, since munin can deliver static stuff, while torrus relies on being dynamic. > > I think it is fine to ship static files in /var/www, but dynamically > > generated stuff which is painless to lose (like the .png files) > > should, IMO, be in /var/cache, and dynamic data which has value (like > > the .rrd files) should be in /var/lib. In my opinion, the value of the > > data should take precedence to its use when judging where to store it. > > /var/cache could be a ram disk and not being backupped, and I could > > surely come up with a situation where /var/www and /var/lib could be > > treated differently storage-, backup- and purge-wise. > > Well, it's /var in any case, which the FHS says is for "variable data > files", so it's unsuitable for fully static files which will never > change (ie. files contained in the data.tar.gz part of the .deb), IMO. Right. We have examples of that though, /var/www/index.html being one of the most prominent examples. > /usr/share strikes me as the proper place for this. Ageed. > /var/cache does > not seem to me like an unreasonable place for the Munin output, based > on the FHS description, though. Yes. > But /var/www seems to be a "Debianism" > that's not mentioned in the FHS, so its intended usage isn't quite > clear to me. Neither it is to me. So I would judge for _my_ packages to put files where I know they're right. > Is a mass bug filing warranted, or is Munin special in > some way that makes it not OK to use /var/www while all the others > should? I think the reality is in between these examples. But, there might be insightful discussion on debian-devel. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
