On Fri, 2012-11-30 at 20:16 +0000, Richard W.M. Jones wrote:
On Fri, Nov 30, 2012 at 09:07:34PM +0200, Nikos Roussos wrote:
> I maintain IDJC , which depends on libshout. The latest version
> though depends on libshout-idjc a fork of the original library, since
> the idjc upstream developer wanted some extra functionality on libshout
> and didn't want to wait for libshout upstream to adopt his changes.
> I've read the relevant documentation  but I'm not sure what's the
> best way to proceed. The good thing that he doesn't bundle his version
> of libshout, but instead he has made it a separate release , which
> could also be packaged for Fedora. But a fork is a fork.
> Should I just make a request for exception and package the forked
> library or should the package be orphaned?
>  https://apps.fedoraproject.org/packages/idjc
>  https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries
>  http://sourceforge.net/projects/idjc/files/
How likely is it that the changes would go back into libshout? Is the
maintainer of IDJC pushing them? Is the libshout maintainer
interested in them?
After discussing it with the developer it seems that some of his changes
include support for non-free codecs (eg. AAC). So the best solution I
can think of is to orphan the package and then move it along with
libshout-idjc to RPMFusion.
comzeradd @ freenode.net