Le mer. 30 janv. 2019 à 05:04, Gergely Gombos <[email protected]> a écrit :
>
> Hi RPMFusion devs,
>
> My name is Gergely Gombos. I've been using Fedora for about 1.5 years and I'm 
> a software developer. I like the FOSS philosophy and using a lot of 
> open-source software in the Javascript world, I'd like to make my 
> contribution, too.
>
> I'm looking for a sponsor, and my first RPM package is 
> "pulseaudio-module-bluetooth-aptx" and its dependency "libldac".
>
> The original project - yet to be merged into upstream Pulseaudio - provides 
> awesome audio quality for Bluetooth headsets via aptX, AAC and LDAC codecs. 
> This is something that is hard to set up even on Windows! And this package 
> works seamlessly on Linux.
>
> Originally this was in a COPR repo, with >100 downloads, but it got deleted 
> due to legal reasons (ffmpeg build dependency). So I hope it will find a new 
> home here since Fedora users are waiting for it.
>
> I've spent quite a lot of time figuring out how RPM packaging works and get 
> this working and (hopefully) conforming to the guidelines - I appreciate your 
> review and help.

Thx for your interest in the project and welcome.

As stated by Leigh, there is a need to verify that libldac is patent
clear according to RedHat Legal or not, then we will introduce in RPM
Fusion free if needed.

Another point is that we have a policy not to replace any
fedora/redhat package. So we you cannot rename the library so it can
install along, then the other way is to conflicts with the fedora
package. End-users will have to remove the fedora package and install
ours.

Also you seems to provide a binary package using a source archive
which name is already in the fedora repo. We used to have a -freeworld
suffix to handle such case when the package is relevant to the free
section and -nonfree suffix when it's relevant to the nonfree section.
Please try to adapt as appropriate.
_______________________________________________
rpmfusion-developers mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to