I think it's not required in a sense that its on/off status is auto-detected at build time (unless you use -DNoVoip=True), and don't think that's what optional dependencies are for - they are for stuff not required at runtime, so it'd seem to be a wrong and misleading thing to do.
There is a minimal version of this PKGBUILD here: https://aur.archlinux.org/packages/telegram-tdlib-purple-minimal-git
Which maybe you can use, it has -DNoWebp=True -DNoLottie=True -DNoVoip=True
and no corresponding dependencies.
Otherwise I think it'd have to be a separate PKGBUILD like that -minimal
one (-novoip
maybe), and idk if adding that on AUR with such packages is a better idea than maybe you removing that from depends=() in PKGBUILD or making some AUR-build-tool do that automatically (they probably have hooks for that).
Pinned Comments
mk-fg commented on 2021-12-07 14:44 (UTC) (edited on 2022-03-18 16:03 (UTC) by mk-fg)
If you're getting error like this on login:
Check https://core.telegram.org/api/obtaining_api_id URL, for generating api_id/api_hash values (only a couple clicks) and specify those for makepkg like this:
WARNING messages should be printed if these values are missing in env during build.
This might be unnecessary in future versions, if these credentials can be specified via the UI there. See tdlib-purple README or https://github.com/ars3niy/tdlib-purple/pull/129 for more up-to-date info.