[MythDora] MythDora 5 MythTV RPM upgrade not working

[Axel Thimm]

On Wed, May 07, 2008 at 02:43:37PM -0400, Jarod Wilson wrote:
> On Wed, 2008-05-07 at 21:24 +0300, Axel Thimm wrote:
> > On Wed, May 07, 2008 at 01:54:01PM -0400, Jarod Wilson wrote:
> > > On Wed, 2008-05-07 at 20:36 +0300, Axel Thimm wrote:
> > > > On Tue, May 06, 2008 at 09:19:03PM -0400, Chris wrote:
> > > > > Update: It looks like the audio noise problem is fixed but I'm seeing 
> > > > > terrible audio sync problems occurring on some channels and it doesn't 
> > > > > recover sync.  Also, CPU usage is through the roof, 85-98% just watching 
> > > > > 720p broadcasts.  1080i ranges 55-75%.  SLIM playback.
> > > > 
> > > > Where previous 0.21 packages performing better? If so do you know
> > > > which package revisions?
> > > 
> > > 0.21-185.6.md5, which is the atrpms 0.21-185.fc8 + config tweaks -- just
> > > default path stuff and the like, nothing in any way invasive. Though its
> > > entirely possible building against a different package set could cause
> > > some variation -- the build host has a mix of atrpms, livna and other
> > > repos atop f8 + f8-updates.
> > 
> > That's why it's better to use the same binaries otherwise we're not
> > really able to determine what's the same and what's not. Are the
> > config tweaks anything that should be in the generic packages to allow
> > mythdora to simply use the ones at ATrpms?
> 
> Maybe, maybe not... At the moment, most of the changes are dependent on
> other things done in mythdora -- creating /storage and a hierarchy
> underneath it for all mythtv-related storage and forcing the user to
> install some themes not included in the base theme package (blootube
> this release, retro last release). We also prefer xine over mplayer.
> 
> http://devel.wilsonet.com/mythdora/mythtv-0.21-mythdora-settings.patch
> http://devel.wilsonet.com/mythdora/mythplugins-0.21-mythdora-settings.patch
> 
> So taking these entirely would require the mythtv packages lay down
> the /storage/* paths, hard-require blootube and blootube-osd[1], as well
> as xine.

I wouldn't hardwire paths (actually /storage is a real mounting point
on many of the systems I've seen doing clustered lvm, not really a
place to default mythtv to, although not many cluster racks will be
doing mythtv I guess ;) - instead why not use FHS standard paths and
symlink them to /storage? That way the packages remain the same, you
are FHS compliant, can share with ATrpms and you still have control
over where the bits land.

BTW I'm currently not sure the packages are 100% FHS compliant in this
respect. If you like we can review this and properly set it in stone.

> [1] I've been meaning to point out that many of the theme packages on
> atrpms.net, including all the blootube variants, are in need of updates
> to behave better with 0.21.

Patches are welcome :)
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/mythdora/attachments/20080507/8a30c231/attachment.bin