[mythtv] Why are themes downloaded to /etc/mythtv?

Raymond Wagner raymond at wagnerrp.com
Sun Dec 11 20:47:59 UTC 2011

On 12/11/2011 06:29, James Courtier-Dutton wrote:
> On Dec 11, 2011 8:06 AM, "Michael T. Dean" <mtdean at thirdcontact.com 
> <mailto:mtdean at thirdcontact.com>> wrote:
> >
> >
> > Actually, I'd prefer not even having a MYTHCACHEDIR.
> >
> > Firefox doesn't let me specify a different location for ~/.mozilla.  Nor
> > does xine allow changing ~/.xine, nor MPlayer its ~/.mplayer, nor DBus
> > ~/.dbus, ...
> >
> > If it's just cache data (once we allow putting the config file
> > elsewhere), I really don't see a good reason to move the cache.
> >
> > Mike
> But i think the issue is that mythbackend does not need terminal 
> interaction. So i think that mythbackend should be treated like an 
> "apache" instead of a frontend like "firefox".
> i.e. Have a main config file in /etc. and mythbackend will look in 
> there for the location of the cache directory.
> Mythfrontend has user terminal interaction, so it is sensible to treat 
> that like a "firefox" and put its config in $HOME.

I still don't understand why you keep harping on this HOME directory 
issue.  Look in your passwd file.  Everyone gets home directories, 
everyone gets login shells.  Looking through the various things I have 
installed, my mail server uses HOME for its storage path, my print and 
cron daemons use HOME for their spoolers, portage uses HOME for its 
default build cache, man uses HOME for its man pages, NUT uses HOME for 
its state data.  The HOME path is nothing more than a place where you 
can configure some aspect of that service.  Some use it, some ignore it, 
some set it to a non-existent or empty path.

The difference between a user and a service account is the ability to 
log in.  Users get a password and a terminal emulator for a shell.  
Services get something that cannot be executed, such that any logins 
fail, or the special 'nologin' application that prints a warning and 
immediately logs back out.

In any case, not having any HOME for mythbackend is simply not a viable 
option.  MythTV does not live inside its own isolated bubble, it calls 
external applications.  There are several XMLTV grabbers that cache data 
in HOME, and several others that store supplemental data in HOME.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.mythtv.org/pipermail/mythtv-dev/attachments/20111211/efc81c74/attachment.html 

More information about the mythtv-dev mailing list