Hi SFLphone developer here, Following #522732, pjsip was removed, that pulled sflphone along with it. For the rational behind this, I mostly agree, pjsip build system is a mess. However, we ship a static copy of the pjproject project in out release repository for just that. We turn off most options to keep only what we need. The old ebuild should mostly work as is with this change: cd daemon/libs/ ./compile_pjsip.sh Download: https://projects.savoirfairelinux.com/attachments/download/14805/sflphone-1.4.1.tar.gz The KDE/Gnome part of the ebuild should be unaffected I know copy of libraries in ebuild are not recommended, but sharing pjproject between multiple apps such as Asterisk and SFLPhone isn't worth the trouble. Reproducible: Always
https://blog.savoirfairelinux.com/en/2015/the-ring-project-decoding-a-decentralized-and-secure-communication-system/ Ring is the evolution of a former project — SFLphone — which has matured over the last ten years and was based on the old concept of centralized data.
http://dl.ring.cx/ring-release/tarballs/ Sorry, but who invents such insane tarball names? I planned to write an ebuild for this software but those tarball names already scared me away.
(In reply to Lars Wendler (Polynomial-C) from comment #2) > http://dl.ring.cx/ring-release/tarballs/ > > Sorry, but who invents such insane tarball names? > I planned to write an ebuild for this software but those tarball names > already scared me away. Ring has not had stable releases so far, hence the snapshots, which have their tarballs marked by the date and commit hash. Not as convenient as stable releases, but a reasonable choice, IMO.
