On Thu, Jan 5, 2012 at 8:53 AM, Jarod Wilson <jarod(a)wilsonet.com> wrote:
On Jan 4, 2012, at 4:26 PM, Richard Shaw wrote:>>> Instead
of bouncing back and forth between bugs, I was hoping that>> things could be hashed
out here instead.>>>> Here's my current status, please let me know if
there's something I>> need to update:>>>> Missing dependencies for
MythTV on EPEL 6.>> --->> lirc [1] (built, pending for testing)>> Yeah,
the Fedora maintainer has been slacking... ;)
Eh, no biggie, it will not be the last requirement resolved, so it
wasn't the hold-up :)
> transcode>> -> pvm [7]>> ->
libmpeg3 [8]>> -> v4l (too old) [9]>> There's a newer v4l in
epel that is designed to co-exist with the distro-provided> v4l, if I'm thinking
clearly.
Yup, see below :)>>> -> mjpegtools-devel (et al.)>> ->
libquicktime-devel (et al.)>> libcrystalhd (disabled due to below)>>
crystalhd support isn't worth the effort, its fairly useless these
days. I'd mostly only> be worried about vdpau and va-api.
Yup. That's the plan.
On Thu, Jan 5, 2012 at 9:02 AM, Jarod Wilson <jarod(a)wilsonet.com> wrote:
On Jan 5, 2012, at 9:49 AM, Richard Shaw wrote:
> I think the biggest roadblock at this point is "v4l" where the RHEL
> version is quite old, however, Hans[1] is trying to appeal to the RHEL
> QA gods to see if he can convince them.
Hm. There's newer v4l-utils in EPEL... But no libv4l. Looks like its been packaged
to
have a private libv4l copy or some such thing. Was thinking that could be used, but
maybe not.
We may be able to, I just having figured out how to yet. When I try to
use that version the transcode build fails because of missing headers
which the new package does not provide. If someone knows a way around
that then we may be back in business.
Or do we just build transcode without v4l support?
See here for the details:
https://bugzilla.redhat.com/show_bug.cgi?id=755343
Thanks,
Richard