Package Details: coolercontrol 1.4.2-1

Git Clone URL: https://aur.archlinux.org/coolercontrol.git (read-only, click to copy)
Package Base: coolercontrol
Description: A program to monitor and control your cooling devices
Upstream URL: https://gitlab.com/coolercontrol/coolercontrol
Licenses: GPL-3.0-or-later
Conflicts: coolercontrol
Provides: coolercontrol
Submitter: codifryed
Maintainer: codifryed (caferen)
Last Packager: caferen
Votes: 30
Popularity: 3.79
First Submitted: 2023-02-07 21:45 (UTC)
Last Updated: 2024-09-28 02:06 (UTC)

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:

sudo systemctl enable --now coolercontrold

Then open the desktop application.

Latest Comments

1 2 3 4 5 6 .. 11 Next › Last »

loathingkernel commented on 2024-10-04 16:26 (UTC) (edited on 2024-10-04 16:28 (UTC) by loathingkernel)

@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 as SRCDEST.
  • 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.

codifryed commented on 2024-10-04 14:30 (UTC)

Hi @loathingkernel,

Thanks for the examples. In those pkgbuilds I see a single build step for all sub-packages. We have no common build process, as all 3 are essentially independent and it appears that a split-package would require building all 3 even if a user wanted to only install 1 of the sub packages.

What benefits do you see to the spit-package over 3 separate packages for coolercontrol?
We might have missed something, but when we researched and analyzed the differences, 3 separate packages seemed to fit the best, especially as in the future coolercontrol-liqctld will be optional and the desktop app is pretty much already optional. The build time for the desktop app alone for example is significant.

loathingkernel commented on 2024-10-03 09:40 (UTC) (edited on 2024-10-03 09:42 (UTC) by loathingkernel)

@codifryed the different build procedures is usually handled by building the package in multiple steps in different subfolders if required (due to source conflicts for example), i.e

  • ppsspp, two builds into two different directories and dependencies per package inside the package_() function
  • glibc
  • mesa, which splits a single build step into multiple packages

From reviewing the whole set of PKGBUILDs I don't see anything that wouldn't fit in the split package paradigm.

codifryed commented on 2024-10-03 08:22 (UTC)

As I understand it @loathingkernel, the split package does not fit our use case.

The repo is the same for the difference packages, but they have very different build processes and require different build functions. Also the dependencies between them will be relaxed in an upcoming release.

loathingkernel commented on 2024-10-02 11:36 (UTC) (edited on 2024-10-02 12:29 (UTC) by loathingkernel)

Why was this package split into three separate pkgbuilds instead of making it a split package?

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!

ptr1337 commented on 2024-07-28 09:36 (UTC)

webkit2gtk-4.1 missing as depend.

ptr1337 commented on 2024-07-20 07:42 (UTC)

Check fails, when compiling in chroot/docker:

==> Starting check()...
packaging/metadata/org.coolercontrol.CoolerControl.metainfo.xml: OK

CoolerControl-Liqctld v1.3.0

System:
    Arch Linux
    Linux-6.9.5-arch1-1-server-x86_64-with-glibc2.39

Dependency versions:
    Python     3.12.4
    Liquidctl  1.13.0
    Finished `release` profile [optimized] target(s) in 0.11s
     Running `target/release/coolercontrold -v`
[2024-07-20T07:38:00Z INFO  coolercontrold] Logging Level: INFO
[2024-07-20T07:38:00Z INFO  coolercontrold] 
    CoolerControlD v1.3.0

    System:
        Linux 20240101.0.204074 Arch Linux
        6.9.5-arch1-1-server

   Compiling tauri v1.6.7
   Compiling tauri-macros v1.4.4
   Compiling coolercontrol v1.3.0 (/tmp/pkg/src/coolercontrol-1.3.0/coolercontrol-ui/src-tauri)
   Compiling tauri-plugin-single-instance v0.0.0 (https://github.com/tauri-apps/plugins-workspace?rev=5e3900e682e13f3759b439116ae2f77a6d389ca2#5e3900e6)
   Compiling tauri-plugin-localhost v0.1.0 (https://github.com/tauri-apps/plugins-workspace?rev=5e3900e682e13f3759b439116ae2f77a6d389ca2#5e3900e6)
   Compiling tauri-plugin-window-state v0.1.1 (https://github.com/tauri-apps/plugins-workspace?rev=5e3900e682e13f3759b439116ae2f77a6d389ca2#5e3900e6)
   Compiling tauri-plugin-store v0.0.0 (https://github.com/tauri-apps/plugins-workspace?rev=5e3900e682e13f3759b439116ae2f77a6d389ca2#5e3900e6)
    Finished `release` profile [optimized] target(s) in 1m 16s
     Running `target/release/coolercontrol -v`

(coolercontrol:13669): Gtk-WARNING **: 07:39:16.776: cannot open display: 
==> ERROR: A failure occurred in check().
    Aborting...
mv: cannot stat '/home/notroot/packages/*pkg.tar*': No such file or directory

1 2 3 4 5 6 .. 11 Next › Last »