@codifryed first of all, thank you for looking into this. I should mention that indeed this might be a little inconvenient from the perspective of a user, but from the perspective of a packager it would be more convenient.
The benefits of a split package, in no particular order of importance.
- It wouldn't require to download the same source three times, although if this is important for the user it can be worked around using
pacman
facilities such asSRCDEST
. - The suggested way of building packages from the AUR is in clean chroots. Building three separate packages for a user that wants all three would require setting up and updating tree separate instances of clean chroots, which is a time-consuming process during building.
paru
for example supports building in clean chroots if configured that way. - It should ensure that all three packages are updated in lock-step, without the potential of mixing different versions of them because one of them was left behind.
Furthermore, my personal opinion is that if this package was eventually to be picked up for packaging in Arch's repos, my experience suggests that it would be combined into a single split package, although that's not something that I can be certain of happening. Making it a split package now would certainly make it easier if it was to happen.
Pinned Comments
codifryed commented on 2024-09-22 19:02 (UTC)
With the release of 1.4.1 CoolerControl has now been spit up into several packages. This requires users to uninstall and then reinstall the application.
See: https://gitlab.com/coolercontrol/coolercontrol/-/issues/347
There's an upside, there's now a binary AUR package
coolercontrol-bin
for less compile time!codifryed commented on 2023-02-07 22:54 (UTC) (edited on 2024-01-06 23:57 (UTC) by codifryed)
Post-installation steps:
Then open the desktop application.