4:52 p.m.
Hello, i'm packaging Mixxx without mp3 support for Fedora repos but i have
a problem, i don't wanna generate a conflict with RPM Fusion repos, Mixxx
are now here (with mp3 support), I think both Mixxx versions can coexist
like Audacity, can you help me with that?
Greetings
6:38 p.m.
New subject: Fwd: Change Mixxx package name
---------- Mensaje reenviado ----------
De: "Tonet Jallo" <tonet666p(a)gmail.com>
Fecha: 22/03/2014 11:52
Asunto: Change Mixxx package name
Para: <rpmfusion-developers(a)lists.rpmfusion.org>
Cc:
Hello, i'm packaging Mixxx without mp3 support for Fedora repos but i have
a problem, i don't wanna generate a conflict with RPM Fusion repos, Mixxx
are now here (with mp3 support), I think both Mixxx versions can coexist
like Audacity, can you help me with that?
Greetings
10:15 p.m.
On Sat, Mar 22, 2014 at 12:52 PM, Tonet Jallo wrote:
Hello, i'm packaging Mixxx without mp3 support for Fedora repos
but i have a
problem, i don't wanna generate a conflict with RPM Fusion repos, Mixxx are
now here (with mp3 support), I think both Mixxx versions can coexist like
Audacity, can you help me with that?
Is it not possible to factor out the libmad code as we did for
qtractor a while ago?
http://cvs.rpmfusion.org/viewvc/rpms/qtractor-freeworld/devel/qtractor-li...
Orcan
1:17 p.m.
Hello, Mixxx have a flags to exclude ffmpeg and libmad, not is necesary
create a patch.
Greetings
El 29/03/2014 17:16, "Orcan Ogetbil" <oget.fedora(a)gmail.com> escribió:
On Sat, Mar 22, 2014 at 12:52 PM, Tonet Jallo wrote:
> Hello, i'm packaging Mixxx without mp3 support for Fedora repos but i
have a
> problem, i don't wanna generate a conflict with RPM Fusion repos, Mixxx
are
> now here (with mp3 support), I think both Mixxx versions can coexist like
> Audacity, can you help me with that?
Is it not possible to factor out the libmad code as we did for
qtractor a while ago?
http://cvs.rpmfusion.org/viewvc/rpms/qtractor-freeworld/devel/qtractor-li...
Orcan
4:11 a.m.
On Mon, Mar 31, 2014 at 9:17 AM, Tonet Jallo wrote:
El 29/03/2014 17:16, "Orcan Ogetbil" escribió:
> Is it not possible to factor out the libmad code as we did for
> qtractor a while ago?
Hello, Mixxx have a flags to exclude ffmpeg and libmad, not is necesary
create a patch.
Well, the qtractor patch we wrote does not just add an option to
disable libmad. It builds the libmad component of qtractor into an
independent shared object which is dlopened by the main program if
exists on the system. This helps with packaging the libmad "binding"
separately.
Best,
Orcan
1:13 p.m.
Mmmmm, but this is not the problem, the problem is the version of mixxx
already in rpmfusion and i need it name will changed to mixxx-freeworld
same to audacity-freeworld.
Sorry if you don't understand some parts, my english is not very good.
Greetings
El 31/03/2014 23:12, "Orcan Ogetbil" <oget.fedora(a)gmail.com> escribió:
On Mon, Mar 31, 2014 at 9:17 AM, Tonet Jallo wrote:
> El 29/03/2014 17:16, "Orcan Ogetbil" escribió:
>> Is it not possible to factor out the libmad code as we did for
>> qtractor a while ago?
> Hello, Mixxx have a flags to exclude ffmpeg and libmad, not is necesary
> create a patch.
Well, the qtractor patch we wrote does not just add an option to
disable libmad. It builds the libmad component of qtractor into an
independent shared object which is dlopened by the main program if
exists on the system. This helps with packaging the libmad "binding"
separately.
Best,
Orcan
2:12 a.m.
Tonet Jallo wrote:
Mmmmm, but this is not the problem, the problem is the version of
mixxx
already in rpmfusion and i need it name will changed to mixxx-freeworld
same to audacity-freeworld.
Sorry if you don't understand some parts, my english is not very good.
His point is, if mixxx can support plugins for the patent-encumbered codecs,
then it can MOVE to Fedora and RPM Fusion can ship a mixxx-freeworld plugin
that works with the Fedora mixxx (the preferred way to package support for
additional codecs in RPM Fusion) rather than a package that Conflicts (a
solution that is only used as a last resort).
Kevin Kofler
3:55 a.m.
Let me see 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?
2014-04-01 21:12 GMT-05:00 Kevin Kofler <kevin.kofler(a)chello.at>:
Tonet Jallo wrote:
> Mmmmm, but this is not the problem, the problem is the version of mixxx
> already in rpmfusion and i need it name will changed to mixxx-freeworld
> same to audacity-freeworld.
> Sorry if you don't understand some parts, my english is not very good.
His point is, if mixxx can support plugins for the patent-encumbered
codecs,
then it can MOVE to Fedora and RPM Fusion can ship a mixxx-freeworld plugin
that works with the Fedora mixxx (the preferred way to package support for
additional codecs in RPM Fusion) rather than a package that Conflicts (a
solution that is only used as a last resort).
Kevin Kofler
4:27 a.m.
On Tue, Apr 8, 2014 at 11:55 PM, Tonet Jallo wrote:
Let me see 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?
Right. But someone needs to write a patch for this, like I did for qtractor.
Best,
Orcan
7:48 p.m.
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.
That been said, that's a special case where everything was plugins, not a
single application.
So whereas you could submit a mixxx-free package in fedora amputated from
it's fully upstream mp3 support via libmad. The RPM Fusion counterpart
coudn't extend the fedora package.
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.
The second choice for me would be to just maintain mixxx in RPM Fusion
instead of fedora as it's a very little disadvantage over having an
incomplete package in fedora.
In this case, you just need to request maintainership of the package,
please see: http://rpmfusion.org/Contributors/CVSRequests
Nicolas (kwizart)
2014-04-09 5:55 GMT+02:00 Tonet Jallo <tonet666p(a)gmail.com>:
Let me see 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?
2014-04-01 21:12 GMT-05:00 Kevin Kofler <kevin.kofler(a)chello.at>:
Tonet Jallo wrote:
> > Mmmmm, but this is not the problem, the problem is the version of mixxx
> > already in rpmfusion and i need it name will changed to mixxx-freeworld
> > same to audacity-freeworld.
> > Sorry if you don't understand some parts, my english is not very good.
>
> His point is, if mixxx can support plugins for the patent-encumbered
> codecs,
> then it can MOVE to Fedora and RPM Fusion can ship a mixxx-freeworld
> plugin
> that works with the Fedora mixxx (the preferred way to package support for
> additional codecs in RPM Fusion) rather than a package that Conflicts (a
> solution that is only used as a last resort).
>
> Kevin Kofler
>
3690
days inactive
3710
days old
rpmfusion-developers@lists.rpmfusion.org
9 comments
4 participants
participants (4)
-
Kevin Kofler -
Nicolas Chauvet -
Orcan Ogetbil -
Tonet Jallo