[ATrpms-users] mythcommflag and mythtranscode in mythtv-frontend, not mythtv-backend?

[Axel Thimm]

On Wed, Oct 04, 2006 at 07:35:49PM -0700, Joe Votour wrote:
> This time when I installed MythTV from RPMs (I've been running SVN for
> quite a while due to needing a custom patch from early in the 0.20 SVN
> cycle) I noticed something that I think is strange.
> 
> Rather than installing "mythtv-suite" on my backend, I installed
> "mythtv-backend" via yum - I saw a post from you that indicated that you
> could do this for "mythtv-frontend".  I notice though that mythcommflag
> and mythtranscode are included in "mythtv-frontend" as opposed to
> "mythtv-backend".
> 
> Aren't mythcommflag and mythtranscode typically run on the server, and not
> the frontend?  I noticed that a bunch of my shows on my backend weren't
> having commercial flagging done, and then found that I had to install
> "mythtv-frontend" in addition to get mythcommflag installed.

That's dumb, of course. Looking at the %files section I see even more
stuff that needs to move from frontened to backend.

Care to take up the task to make a better file distribution within
mythtv? For some binaries/files one would need to ask the mythtv
developers.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20061005/d4a6f35f/attachment-0001.bin