mbox series

[bug#57675,v10,0/9] gnu: telegram-desktop: Update to 4.2.0.

Message ID y764jwya1tw.wl-hako@ultrarare.space
Headers show
Series gnu: telegram-desktop: Update to 4.2.0. | expand

Message

Hilton Chain Sept. 23, 2022, 9:15 a.m. UTC
v9 -> v10: Use revision rather than %telegram-version.

Hilton Chain (9):
  gnu: telegram: Revision-based version for additional sources.
  gnu: Add abseil-cpp-cxxstd17.
  gnu: extra-cmake-modules: Update to 5.98.0.
  gnu: kcoreaddons: Remove trailing #t.
  gnu: kcoreaddons: Update to 5.98.0.
  gnu: webrtc-for-telegram-desktop: Update to 621f3da5.
  gnu: Remove libvpx-for-telegram-desktop.
  gnu: telegram-desktop: Update to 4.2.0.
  gnu: telegram: Remove unused variables.

 gnu/local.mk                                  |   2 +
 gnu/packages/cpp.scm                          |   9 +
 gnu/packages/kde-frameworks.scm               |  23 +-
 ...gram-desktop-allow-disable-libtgvoip.patch | 125 ++++
 ...r-telegram-desktop-fix-gcc12-cstdint.patch |  21 +
 gnu/packages/telegram.scm                     | 642 +++++++++---------
 6 files changed, 486 insertions(+), 336 deletions(-)
 create mode 100644 gnu/packages/patches/telegram-desktop-allow-disable-libtgvoip.patch
 create mode 100644 gnu/packages/patches/webrtc-for-telegram-desktop-fix-gcc12-cstdint.patch


base-commit: a57c4eff6bbdcff79294fa15ecb95ab2b3c55bb4

Comments

Liliana Marie Prikler Sept. 23, 2022, 2:54 p.m. UTC | #1
Am Freitag, dem 23.09.2022 um 17:15 +0800 schrieb Hilton Chain:
> v9 -> v10: Use revision rather than %telegram-version.
> 
> Hilton Chain (9):
>   gnu: telegram: Revision-based version for additional sources.
I don't think you're improving anything here really.  These variables
are already labeled "for-telegram-desktop", so using the telegram-
desktop version here makes natural sense.  We can still use Guix
revisions if some component needs updating and we find out later
(through bug reports etc.)  The origin rebuilds are not a big deal
whatsoever.  For one, we have store deduplication, for the other, the
huge cost is the actual building of telegram-desktop, which we cannot
abstract away with while only half-ass unbundling stuff.

Thus, as long as these packages have no use outside of building
Telegram, I'd very much prefer a scheme that lets us update them all
easily by just changing one version and a bunch of hashes.

Cheers