| Message ID | y76mtasddas.wl-hako@ultrarare.space |
|---|---|
| Headers | show |
| Series | gnu: telegram-desktop: Update to 4.2.0. | expand |
Am Mittwoch, dem 21.09.2022 um 22:15 +0800 schrieb Hilton Chain: > v7 -> v8: > 1. Add telegram-desktop 4.1.1, which does not require an updated > cmake-extra-modules. > 2. Remove %telegram-version, to avoid downloading all the sources > each time updating > telegram. > > v8 -> v8 RESEND: Finally figured out mime stuff..... > > Hilton Chain (7): > gnu: Add abseil-cpp-cxxstd17. > gnu: webrtc-for-telegram-desktop: Update to 621f3da5. > gnu: telegram-desktop: Update to 4.1.1. > gnu: extra-cmake-modules: Update to 5.98.0. > gnu: kcoreaddons: Remove trailing #t. > gnu: kcoreaddons: Update to 5.98.0. > gnu: telegram-desktop: Update to 4.2.0. Is there a *good* reason for the intermediate step? Also, the %telegram-version was so that we can update the submodules (whose hashes I assume change with updated telegrams) more easily. Is there a better versioning scheme for those? Cheers
>Is there a *good* reason for the intermediate step? No.... >Also, the %telegram-version was so that we can update the submodules >(whose hashes I assume change with updated telegrams) more easily. Is >there a better versioning scheme for those? Not all submodules need updating when new releases out. Another approach is just cloning recursively and remove all sources within ThirdParty folder via snippet, then only tracking version changes of these removed ones (or unbundle them when applicable).