<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2014-10-22 13:58 GMT+02:00 Rich Freeman <span dir="ltr"><<a href="mailto:r-mythtv@thefreemanclan.net" target="_blank">r-mythtv@thefreemanclan.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On Wed, Oct 22, 2014 at 4:47 AM, Andréas Kühne <<a href="mailto:andreas@kuhne.se">andreas@kuhne.se</a>> wrote:<br>
> I have been following this discussion from the sidelines and I think<br>
> that the entire discussion is really a bit wrong.<br>
<br>
</span>So, I get that I'm not paying for MythTV. I don't believe that this<br>
automatically shields its developers from /any/ criticism. Free<br>
software is a community. I might not contribute to MythTV, but<br>
perhaps I contribute to something that a MythTV developer uses. Or,<br>
maybe Fred uses software I contribute to, and Fred contributes to<br>
software that a MythTV developer uses. The bottom line is that while<br>
we aren't compensated for our time directly, we all participate in a<br>
community where we'd probably prefer that others take into account our<br>
preferences.<br>
<br>
Now, there are limits to that. In the end as contributors to free<br>
software we get to decide where those limits are.<br>
<span class=""><br>
> I for one would really welcome the ability to make MythTV more of an<br>
> appliance than a program that you have to be somewhat of a DevOp to use. I<br>
> know there was an Australian based company selling MythTV computers for<br>
> "normal" people, and I think that a new version of that would be great for<br>
> the TV ecosystem.<br>
<br>
</span>I don't think the term "appliance" is a good analogy here.<br>
<br>
An appliance is something that is pre-packaged. You plug it in and<br>
turn it on. A Tivo is an appliance.<br>
<br>
Simply moving to a bundled, embedded MySQL database is not going to<br>
make MythTV an appliance. I can't just install the package and<br>
magically get a working system. If my distro uses the ext4 filesystem<br>
with ordered journaling (which is the likely default on 99% of them)<br>
the MythTV embedded database is probably going to have abysmal<br>
performance. If everything does work fine, I still don't have IR<br>
remote control support. I still need to pick a distro, which may or<br>
may not include MythTV in its repository, and which may or may not<br>
provide updates to it.<br></blockquote><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Something like Mythbuntu could be considered more appliance-like,<br>
addressing just about everything but the hardware. I've never used<br>
it, but I assume that it comes with MythTV and MySQL pre-installed and<br>
properly configured on appropriate filesystems/etc, and with a kernel<br>
that has support for all the tuner cards and such enabled. That just<br>
demonstrates that you can have appliance-like behavior without moving<br>
to embedded MySQL.<br>
<br>
The ultimate appliance would have to be sold in a box and have a power<br>
cable attached.<br>
<br>
I don't think that moving to an embedded MySQL really solves the<br>
"appliance problem" at all. That is really a problem for a systems<br>
integrator. I don't object if MythTV wants to create a linux distro<br>
on the side and ensure that it always has a smooth upgrade path. I<br>
don't think the solution is for them to basically embed a whole distro<br>
in the MythTV program itself. Keep it modular, and then everybody can<br>
integrate it however they feel is best. The MythTV devs could set a<br>
policy that they'll only accept bug reports if they can be reproduced<br>
on the official MythTV distro, though I wouldn't encourage that.<br>
<br>
--<br>
Rich<br>
<div class=""><div class="h5">_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<a href="http://wiki.mythtv.org/Mailing_List_etiquette" target="_blank">http://wiki.mythtv.org/Mailing_List_etiquette</a><br>
MythTV Forums: <a href="https://forum.mythtv.org" target="_blank">https://forum.mythtv.org</a><br>
</div></div></blockquote></div></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br class="">Yes I know that it won't be solved by moving to an embedded database. I'm just saying that it's a step in that direction, and this is something I think MythTV could be used as. Especially because the alternatives are extremely locked down and are usually not good implementations of a TV environment.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Regards,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Andréas</div></div>