<div dir="ltr"><div class="gmail_extra">Previous case of a package already in RPM Fusion then submitted to fedora with different options was gstreamer-plugin-bad introduced as gstreamer-plugins-bad-free in fedora while been adapated in RPM Fusion at the same time.<br>
</div><div class="gmail_extra"><br></div><div class="gmail_extra">That been said, that's a special case where everything was plugins, not a single application.<br></div><div class="gmail_extra">So whereas you could submit a mixxx-free package in fedora <span id="result_box" class="" lang="en"><span class="">amputated from it's fully upstream mp3 support via libmad. The RPM Fusion counterpart coudn't extend the fedora package.<br>
<br></span></span></div><div class="gmail_extra"><span id="result_box" class="" lang="en"><span class="">Best would be to have mixxx binary to "dlopen" libmad so introducing mixxx within fedora would not lose any upstream feature that users will need in some corner cases.<br>
<br></span></span></div><div class="gmail_extra"><span id="result_box" class="" lang="en"><span class="">The second choice for me would be to just maintain mixxx in RPM Fusion instead of fedora as it's a very little </span></span><span id="result_box" class="" lang="en"><span class="">disadvantage over having an incomplete package in fedora.<br>
</span></span></div><div class="gmail_extra"><span id="result_box" class="" lang="en"><span class="">In this case, you just need to request maintainership of the package, please see: <a href="http://rpmfusion.org/Contributors/CVSRequests">http://rpmfusion.org/Contributors/CVSRequests</a><br>
<br></span></span></div><div class="gmail_extra"><span id="result_box" class="" lang="en"><span class="">Nicolas (kwizart)<br></span></span></div><div class="gmail_extra"><br><br></div><div class="gmail_extra"><div class="gmail_quote">
2014-04-09 5:55 GMT+02:00 Tonet Jallo <span dir="ltr"><<a href="mailto:tonet666p@gmail.com" target="_blank">tonet666p@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div style="font-family:arial,helvetica,sans-serif"><span lang="en"><span>Let me see</span> <span>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>:<div>
<div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>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><font color="#888888"><br>
Kevin Kofler<br>
</font></span></blockquote></div></div></div><br></div>
</blockquote></div><br></div></div>