On Thu, 2010-01-14 at 14:00 +0000, Mario Limonciello wrote:
> The problem is that this ships in the myth plugins package not mythtv
> package.
So is the installation of these cron jobs a direct result of "make
install" in the myth package? i.e. is this a myth packaging error or a
{myth,u}buntu packaging error?
> Not sure there is much we can do about it because of that.
Well, at a minimum, the cron script could ask some sort of "am in the
backend" question and bail out if not. But you know, even that I don't
particularly agree with, because this script is packaged with mythvideo,
and (AFAIU) mythvideo {w,sh}ould not be installed on a pure (i.e. no FE)
backend machine.
But then on the hand again, does "Video" metadata belong on the backend
if it's a frontend package?
I think there is a severe personality disorder deep in this Jamu stuff.
That or I am just not understanding it correctly.
On Thu, 2010-01-14 at 14:00 +0000, Mario Limonciello wrote:
> The problem is that this ships in the myth plugins package not mythtv
> package.
So is the installation of these cron jobs a direct result of "make
install" in the myth package? i.e. is this a myth packaging error or a
{myth,u}buntu packaging error?
> Not sure there is much we can do about it because of that.
Well, at a minimum, the cron script could ask some sort of "am in the
backend" question and bail out if not. But you know, even that I don't
particularly agree with, because this script is packaged with mythvideo,
and (AFAIU) mythvideo {w,sh}ould not be installed on a pure (i.e. no FE)
backend machine.
But then on the hand again, does "Video" metadata belong on the backend
if it's a frontend package?
I think there is a severe personality disorder deep in this Jamu stuff.
That or I am just not understanding it correctly.