I would love to help with further packaging/development (primarily jibri). So: Would you be so kind to put the jitsi stuff into a separate git repo? With that, it would be much easier for me to submit PRs.
Cheers -Fritz
BTW: There will be a legal problem with a dependency for jibri on fedora:
Currently, ffmpeg is not included in fedora (AFAIK for legal reasons). Instead, it is available on rpmfusion. This implies, that any jibri (jitsi?) package would preferably be distributed on rpmfusion as well. Am I right?
BTW2: Initially, i tried to contact you directly via email to the address shown in your FAS profile. Unfortunately, that bounced. Just in case you wondering why I use an ussue for this.
-Fritz
Hi, thank you, any help is greatly appreciated.
I already copied everything over to the new repo here, though I haven't built from it yet. I originally made this shared one as a collection for small tools I used on my machines, but it has clearly outlived its usefulness.
Regarding Jibri: Yes, that is an issue. However, Jibri only requires Ffmpeg at runtime, so it should be OK to built & distribute it via Copr, it just will not be installeable if people don't have RPMFusion enabled.
Longer term, I'd quite like to get normal Jitsi into Fedora proper and Jibri into RPMFusion, but unfortunately, I don't see me unbundle all the Java/Node stuff so ...
Thanks for notifying me about the FAS email, I'll have to check that - it should work!
P.S.: DId you send the mail to the lcts@fp.o alias or the actual email address?
Actually, it was my fault (typo). See #6
If you want, you can have a look at the Jibri package. I haven't touched it in a while, but It already builds without issues. The runtime dependencies need sorting out to make it actually usable, so that would be the next step. It will need RPMFusion for sure.
As you have seen already, I migrated the repo. I'll rebuild the packages from there today.
Metadata Update from @lcts: - Issue status updated to: Closed (was: Open)