Hi Tore,
On Mon, May 09, 2005 at 08:18:00AM +0200, Tore Anderson wrote:
> I'm a bit uncertain here. A quick "apt-file search -x \^var/www" show
> 60 packages containing the /var/www directory, including packages
> similar to Munin (cricket and mrtg). For some reason, Munin itself
> didn't show up on that list, so there may be even more of them if I
> goofed up the apt-file command.
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.
> Most of these, like Munin, only create a subdir under /var/www. The
> way I interpreted the passage you quoted above when creating the
> initial package, was something like «Web Application shold try to avoid
> storing files in the Web Document Root [, but rather create it's own
> subdir in it]».
I do not concur with that interpretation, since the policy quite
clearly states that packages should use /usr/share/doc/package (which
is wrong, btw, since nothing should rely on /usr/share/doc being
present).
> This seems to be in accordance with current practise
> (to compare with the 60 packages above, only 10 packages ship files
> in /etc/apache{2,}/conf.d/, and half of these doesn't contain web
> applications at all, but Apache modules.
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.
> Another thing that makes me even more uncertain about how to interpret
> that Policy paragraph is this: «[...] and register the Web Application
> via the menu package.» As far as I know, there's no way to use the
> menu package to register web applications in a web server, so it makes
> me wonder if this passage is at all meant for packages such as Munin.
I have discussed this on #d-d. Formally, the idea is that web
application register with the menu package and the web swerver queries
menu for the packages being installed and configures itself
apropriately. That mechanism seems not to be in wide use though.
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]
