[mythtv-users] [old] Re: XvMC and libmpeg2 to be dropped in 0.25

[Ryan Patterson]

On Wed, Feb 9, 2011 at 9:44 AM, Brian J. Murrell <brian at interlinx.bc.ca> wrote:
> On Wed, 2011-02-09 at 08:38 -0500, Ryan Patterson wrote:
>> Can you
>> swap a different design of engine block into your car without also
>> changing the heads and manifolds?
>> No, all those things must match
>> each other.
>
> OK.  To play along with the way-too-overstrained car analogy... You are
> talking about trying to interchange what I would call "core components".
> Of course the parts of the engine must match just as I would not expect
> to be able to mix and match different versions of myth backend
> components in a single back end.
>
> But on my 10 year old car, I can use today's new wheels on it.  Why?
> Because there are interface standards in place that manufacturers of
> today's new wheels can meet to be interoperable.

But the frontend and backend of mythtv are core components.  Your
example of changing wheels because of a published standard is directly
analogous to changing the remote control on your mythTV frontend.  And
yes that is easily doable because MythTV uses the published LIRC API
for remote controls.

>> Can you name one of these other software projects you are talking
>> about?
>
> How about NFS?  I can mix and match any NFS3 clients and servers without
> anyone whining that they refuse to work with somebody else due to
> version mismatch.
>
> How about web browsers and servers?  There not only can I mix and match
> versions of HTML I can mix and match products even.
>
> How about LDAP.  Again, I can even mix and match products there.
>
> Shall I go on?

Sorry those examples are not comparable at all.  Those projects
support industry standards which take years (or decades) for new
versions to be released.  MythTV uses an internal protocol and
database structure.  It is really apples and oranges.

>> And before you respond please ask yourself, "why am I using
>> MythTV instead of this other project?"
>
> Because NFS is file sharing software and not a PVR?
>
>> That might highlight the fact
>> these other projects are really not comparable to MythTV.
>
> The problem is that I am talking in generalities and you have boxed
> yourself into thinking specifically of PVR software.

Sorry I guess I jumped to the conclusion that you wanted to use MythTV
as a PVR.  That was wrong of me.  I didn't mean to put words in your
mouth.

Now can you please explain how to use MythTV as a replacement for NFS?

-Ryan