Richard Shaw left as an exercise for the reader: > Yes, there's a number of examples but audacity and sox are two. What we do > at RPM Fusion is create a new package there that depends on the package in > Fedora and either append -freeworld (just patent issues, like ffmpeg which > are in the free repo), or append -nonfree for packages that depend on "free > as in beer" instead of "free as in speech" libraries. > > There are a few requirements though to make this work (and I'm not an > expert here so correct me if I'm wrong!) > 1. The library needs to be dlopen()'ed from the main package so it'll still > function without the "extra" packages from RPM Fusion. > 2. All the bits common to the main package need to be excluded from the RPM > Fusion package since we can't (and don't want to) have redunded files in > the package. This may look like "libnotcurses-ffmpeg.so.<soname}" which > would be the only payload in the RPM Fusion -freeworld package. This is exactly how I intend to structure my "notcurses-minimal" for Debian, so it oughtn't be much extra work, excellent: https://github.com/dankamongmen/notcurses/issues/339 Alright, I'll look into this. BTW, while I've read the Packaging Guidelines at https://docs.fedoraproject.org/en-US/packaging-guidelines/, there seem to be some operational details that I'm missing. For instance, it seems I need file a bug once I have my source and binary RPMs -- where can I find details on the necessary information in that bug? Sorry if I've overlooked it :/. -- nick black -=- https://www.nick-black.com to make an apple pie from scratch, you need first invent a universe. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
