<div dir="ltr"><br><br><div class="gmail_quote">On Thu, Sep 4, 2008 at 6:31 PM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On 09/04/2008 05:14 PM, Jerome Yuzyk wrote:<br>
> Hmmmm.. that could delay me a bit. Is there anywhere I can find out what's<br>
> different in the bindings between 0.20 and 0.21(-fixes)? If they're not<br>
> drastic then I could start working with what I have and update when I<br>
> upgrade. I do have a test rig though - no tuner - I could maybe use it to<br>
> develop on. I really don't want to rush to upgrading or move to a<br>
> source-compiled install - I need my Myth!<br>
<br>
</div>A test rig with 0.21-fixes (or trunk, since it's a test rig) would be<br>
your best bet. There's not really any documentation of the changes,<br>
other than the commits as listed at <a href="http://svn.mythtv.org/" target="_blank">http://svn.mythtv.org/</a> . As a<br>
matter of fact, there really isn't any documentation for the bindings<br>
other than the scripts that already use them.<br>
<br>
Normally, I'd recommend you do all work on trunk, but there really<br>
haven't been changes of any significance to the Perl bindings since the<br>
0.21 release, so in this case, if you're willing to do the work on<br>
0.21-fixes, someone else (probably even me) would verify/update the<br>
scripts for trunk. Therefore, if you'd prefer to run 0.21-fixes on your<br>
test rig (allowing you to use packages, and use the test rig to plan for<br>
your 0.21-fixes upgrade of your production systems), feel free to do it<br>
that way.<br>
<br>
Mike<br>
<div></div></blockquote><div><br><br>Been playing <a href="http://myth.find_orphans.pl">myth.find_orphans.pl</a>, it seems to me that I get a number of false positives for "unknown files" due to having overlapping storage groups on multiple backends. The reason is because it's pulling the list of known files for a single backend, so files attributed to another backend in the same storagegroup are seen as unknown files.<br>
<br>What I'm debating is whether it's "better" behavior to simply disable the hostname check and check for all files or to check unknown files against other backends.<br><br>Anyone have a strong opinion?<br>
<br>Ry <br></div></div><br></div>