Reading the new net-im/telegram-desktop-1.9.9.ebuild, it seems it uses bundled media-libs/rlottie instead of packaged.
Since I've used another overlayed telegram ebuild before, which linked to standalone rlottie, probably we can switch painlessly to media-libs/rlottie from portage tree.
It is planned, problem is that it does not have a release or stable ABI.
Ideally I’d wait til it gets a tag, but we can add a dep if at least it gets a subslot.
Also it’ll need a pkgconfig patch, pretty trivial one.
Unbundling tgvoip also planned, just need more time.
re-checked, we still have to use bundled rlottie, otherwise it may crash on some stickers with system-installed one.
pkg-config patch no longer needed though.
changes we need could be probably backported to our rlottie ebuild
but idk, no longer applies to current master and can be a bit painful to maintain in the long run
adding juippis to CC as rlottie maintainer, just fyi, no action needed right now.
They released 0.1 upstream. Maybe it's easier to point a working dependency, or carry patches now?
I added a subslot because the ABI has broken already before a release, I just _hope_ they will now update their sonames with breaking releases.
thanks for the ping wrt 0.1, that's something =)
I'll talk with telegram guys. they use older patched version of rlottie, maybe they can re-base on new version.
patches need to be re-based every release. unbundling is not super-urgent and I'm ok with bundled lib for now until upstream makes up their mind.
telegram is kinda complicated beast and it has to work on linux and windows and macOS, so moving internal libs it not that easy. Everything else except couple header-only libs is unbundled.