On Mon, Mar 24, 2008 at 05:23:00PM +0200, Ville Skyttä wrote:
On Monday 24 March 2008, Axel Thimm wrote:
> Whatever the hardwired defaults at compile time the
> /etc/sysconfig/vdr takes precedence. So the package's scripts can
> easily autoadjust to whatever situation.
Good to hear you know better; I expect to see code to back that up if the
draft passes with a mandate to change the dirs :)
Sure, that's what the FPC's jobs is: to go hunt all packages and fix
them. Good that I'm not a member anymore ;)
Of course, the more serious answer is that this is the packager's job.
> But that would be wrong. One of the main FHS aspects is that a
> package [...]
We already do some things "wrong" wrt the FHS, for example
/etc/rc.d/init.d and /usr/libexec.
So that justifies breaking even more?
I'm not aware of much movement in getting those fixed
Well, check the todo lists and your IRC logs, I was trying to get the
libexec stuff addressed and some steps where done, including an
official submission for a change in the FHS, but it now needs a new
(Fedora) driver to get this pushed further.
So things are done to get Fedora in sync with FHS. I'm not aware what
the /etc/rc.d/init.d issues are to comment on that, but if there's a
deviation the FPC should look at it (if it hasn't done so already).
> Just to reiterate: The /srv/vdr folder currently breaks all
> /srv/<domain> setups.
Sure, if you happen to have a <domain> dir called vdr there for some other
Of if my scripts run over these folders and suddenly assume I'm
hosting a "vdr" domain. There are reasons the FHS explicitely forbids
vendors to mess in there.
Similar things could be said about /var/lib/vdr or /var/spool/vdr.
No, the (limited) freedom of choice in the layout to the user/admin is
solely under /srv (and /opt, /usr/local).
Axel.Thimm at ATrpms.net