<br><br><div class="gmail_quote">On Thu, Jun 23, 2011 at 8:29 PM, Orcan Ogetbil <span dir="ltr"><<a href="mailto:oget.fedora@gmail.com">oget.fedora@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Thu, Jun 23, 2011 at 2:17 PM, Fernando Lopez-Lezcano wrote:<br>
> On 06/23/2011 01:08 AM, Er wrote:<br>
</div><div class="im">>> I just got few questions :<br>
>> - Why ffado-test's absent from the ffado package? As far as I know it's<br>
>> needed to set the clock source of the device. It might be a good thing<br>
>> to add it... or maybe there a good reason for it :)<br>
><br>
> Ffado is part of Fedora now, maybe the maintainer is on this list?<br>
> Otherwise I would suggest filing a bug report with a request for its<br>
> inclusion in RedHat's bugzilla.<br>
<br>
</div>When the package was under review, we had a discussion about including<br>
the tests. I do not remember the exact details, but we ended up<br>
excluding them for a few reasons: Some tests were outdated and failed<br>
to compile (this might have changed since); some of the tests were<br>
just unit tests for helping the actual ffado developers, and we<br>
concluded that they won't do much help to end users.<br>
<br>
Of course, if users find tests useful, we can add them to the RPM<br>
package, or just make a new ffado-tests subpackage. As Fernando<br>
suggested, please file a bug in <a href="http://bugzilla.redhat.com" target="_blank">bugzilla.redhat.com</a> against component<br>
libffado.<br>
<br>
Thanks,<br>
Orcan<br>
<div class="HOEnZb"><div class="h5"></div></div></blockquote><div><br></div><div>I was attempting to add submit a bugzilla for this but was unable to find "ffado" or "libffado" in the list of components.</div>
<div><br></div><div>Also, what's missing is the "ffado-test" program. I'm not sure about the "tests failing to compile" and such that is being discussed above. The program is probably poorly named since the functionality we use it for wouldn't be considered "testing" (eg, "ffado-test ListDevices" or "ffado-test BusReset").</div>
<div><br></div><div>Any idea how we can get it back?</div><div><br></div><div>Thanks,</div><div>Steve</div></div><br>