Skip to content
GitLab
Closed
Issue created by Jami Bot@RingBotMaintainer

Patched packages

Issue generated from Tuleap's migration script. Originally submitted by: szotsaki (szotsaki)

I would like to package Ring for openSUSE, but as soon as I got to PJSIP, it becames really hard.

The problem is that you patched an upstream package (pjsip, among others) which already has an RPM package and normally should be included into the .spec file as a dependency.

However, after patching it's become binary incompatible with the upstream version. This causes when I release the Ring RPM, it will provide its own PJSIP .so file which will clearly conflict with the original one.

I understand that your patches haven't been let in for a long time but unfortunately, the current solution is a packaging nightmare. I see three solutions:

  1. Ping PJSIP developers even more.
  2. Make GnuTLS optional and revert back to LibreSSL/OpenSSL.
  3. (Probably the best): fork PJSIP as PJSIP-Ring and I can create a separate package which can co-exist with the original PJSIP.