commit 64f6748b410c88063c98aafcdebbfb788411a76f
Author: lucascouts <lucascs@protonmail.com>
Date: Tue Sep 8 06:41:23 2026 -0300

add(media-libs/tlottie-0.1.0_pre20260906), fix(net-im/telegram-desktop-7.2.7): the 7.2 series swapped bundled rlottie for system tlottie

Upstream replaced the bundled media-libs/rlottie with tlottie, a Rust library,
in the 7.2 series and deleted Telegram/ThirdParty/rlottie outright. The
auto-bump from 7.1.2 carried `rm Telegram/ThirdParty/rlottie/CMakeLists.txt ||
die` forward, so every merge died in src_prepare: the only 7.2.7 ebuild in the
tree could not be installed at all.

Dropping that line is half the fix. On Linux tlottie is not bundled either --
cmake/external/tlottie does find_library(tlottie REQUIRED) -- so the series
also gained a dependency, and removing the rm alone just moves the failure from
src_prepare to src_configure.

media-libs/tlottie pins the exact commit tdesktop names in
Telegram/build/prepare/prepare.py (758c7cb744), builds it with upstream's own
recipe (cargo rustc --crate-type staticlib --features c-api) and installs the
static archive plus the C API header where find_library and find_path look for
them. RUST_MIN_VER follows upstream's pin of 1.96.1: src/renderer/cpu/simd/
avx512.rs needs intrinsics stable only since 1.89, and no lower version is
claimed to work anywhere. KEYWORDS includes ~arm64 because neon.rs sits beside
the x86 backends.

The archive is linked statically, so no soname can catch ABI drift. The
packages.toml record therefore carries hold = true, and the correct commit is
whatever prepare.py names, never the newest on main -- measured 2026-09-08,
main was already two days ahead of the pinned revision.

Verified end to end: tlottie builds and installs with all 11 C API symbols
surviving the portage strip, telegram-desktop completes prepare, configure,
compile and install, and the resulting Telegram binary carries the same 11
tlottie_* symbols at real addresses, with no undefined reference and no QA
notice.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>