<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [mythtv-users] A plea for some consideration
for the p</title></head><body>
<div>At 11:54 AM -0400 8/8/12, Joseph Fry wrote:</div>
<blockquote type="cite" cite>
<blockquote>Well, that certainly stirred up the hornets nest! One of
the best things about MythTV (and other Linux/UNIX apps) is
the</blockquote>
<blockquote>involvement of a huge range of users and developers who
come to the aid of other struggling users with (mostly) helpful<br>
comments and suggestions.<br>
<br>
The comments have been very valid, and yes, I could have just
installed the MythTV packages. However, I'd still have<br>
this (<a
href="http://www.gossamer-threads.com/lists/mythtv/users/525274"
>http://www.gossamer-threads.com/lists/mythtv/users/525274</a>)
problem. Last time I used the distribution packages I<br>
had another sound issue (or was it the dreaded lirc?) which I could
only resolve with the latest source at the<br>
time. Marius Ducea has some very apt comments here (<a
href="http://www.ducea.com/2008/01/16/source-or-package-install/"
>http://www.ducea.com/2008/01/16/source-or-package-install/</a>). I
want<br>
to unclutter the MythTV menus and not install packages that I don't
use so a source build is needed. I'd also still have<br>
to fix this (<a
href="https://bugs.launchpad.net/mythbuntu/+bug/1004974"
>https://bugs.launchpad.net/mythbuntu/+bug/1004974</a>) to fix the
Mythbuntu theme which a "user" (ie. spouse)<br>
spotted within two minutes of using the new system.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>I think we can all agree that Mythtv
documentation is lacking somewhat. Please don't take this the
wrong way, but rather than asking someone else to improve it, why
don't you make it your personal mission. Perhaps write a
distribution agnostic compile-from-source guide (with notes for saving
time on your distro by using precompiled dependancies). Sure, it
will take a while, especially because your actually trying to figure
everything out as you go.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>The reason that such documentation
doesn't exist is because almost no one does this, and those that do
have no need for documentation. Perhaps you can outline the
reasons why someone would want to build it manually.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>...</blockquote>
<div>Instead of documentation--read the source, of one of the
packager's recipes! I've been working on using MacPorts to build
Myth. The osx-packager.pl script was easy enough to follow to
determine the necessary dependencies on OS X. There are a couple
of other packaging scripts in the Packaging repository on GitHub.
If they are being used regularly, you have pretty good assurance that
the dependencies are complete and up-to-date. After that, the
configure script output summarizes what has been found or not.
Lather, rinse and repeat a couple (dozen) times and 'Bob's your
uncle'!</div>
<div><br></div>
<div>Craig</div>
<div><br></div>
<div><br></div>
</body>
</html>