<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><span id="result_box" class="" lang="en"><span class="">Let me see</span> <span class="">if I understood, you say i can package a mixxx without mp3 support for Fedora repo and other package mixxx-freeworld with only mp3 plugins for RPM Fusion, right?<br>
</span></span></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-04-01 21:12 GMT-05:00 Kevin Kofler <span dir="ltr"><<a href="mailto:kevin.kofler@chello.at" target="_blank">kevin.kofler@chello.at</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">Tonet Jallo wrote:<br>
> Mmmmm, but this is not the problem, the problem is the version of mixxx<br>
> already in rpmfusion and i need it name will changed to mixxx-freeworld<br>
> same to audacity-freeworld.<br>
> Sorry if you don't understand some parts, my english is not very good.<br>
<br>
</div>His point is, if mixxx can support plugins for the patent-encumbered codecs,<br>
then it can MOVE to Fedora and RPM Fusion can ship a mixxx-freeworld plugin<br>
that works with the Fedora mixxx (the preferred way to package support for<br>
additional codecs in RPM Fusion) rather than a package that Conflicts (a<br>
solution that is only used as a last resort).<br>
<span class="HOEnZb"><font color="#888888"><br>
Kevin Kofler<br>
</font></span></blockquote></div><br></div>