Package Details: asusctl 6.0.12-0.1

Git Clone URL: https://aur.archlinux.org/asusctl.git (read-only, click to copy)
Package Base: asusctl
Description: A control daemon, CLI tools, and a collection of crates for interacting with ASUS ROG laptops
Upstream URL: https://asus-linux.org
Keywords: anime asus matrix rog
Licenses: MPL-2.0
Conflicts: gnome-shell-extension-asusctl-gnome
Submitter: fabiscafe
Maintainer: fabiscafe
Last Packager: fabiscafe
Votes: 17
Popularity: 0.62
First Submitted: 2021-09-18 11:01 (UTC)
Last Updated: 2024-08-31 21:34 (UTC)

Pinned Comments

fabiscafe commented on 2023-06-13 21:53 (UTC) (edited on 2024-05-11 23:43 (UTC) by fabiscafe)

Official Setup Guide

https://asus-linux.org/guides/arch-guide/

Merge/Pull Requests / Bugreports

https://gitlab.archlinux.org/fabiscafe/asusctl_aur

Known Issues

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

kojq commented on 2022-12-07 03:01 (UTC) (edited on 2022-12-07 03:02 (UTC) by kojq)

I suppose it may be helpful for some to note 4.5.4 changes:

  • ROGCC:: Allow ROGCC to run without supergfxd
  • ROGCC: Tray/notifs now reads dGPU status directly via supergfx crate (supergfxd not required)
  • Add rust-toolchain to force minimum rust version

kojq commented on 2022-12-05 15:13 (UTC)

@fabiscafe Sounds good, thanks.

fabiscafe commented on 2022-12-05 10:05 (UTC)

@kojq it's only a build-time dependency. They are not required for the installation of asusctl. If you don't want to have make-dependencies at all on your system I recommend to use a build chroot. Paru also supports this, if you prefer to use a helper.

kojq commented on 2022-12-05 06:42 (UTC)

The dependencies didn't seem required for asusctl alone, that's all.

fabiscafe commented on 2022-12-04 21:27 (UTC)

@kojq I don't think that's possible. Both are part of the same source package, so it will build both of them anyways. I wonder why you care about build dependencies?

kojq commented on 2022-12-04 19:40 (UTC)

@fabiscafe Okay. Is it possible the make-deps be just for rog-control-center with seperate PKGBUILDs?

fabiscafe commented on 2022-12-04 18:59 (UTC)

@kojq ahh OK. Both, asusctl and rog-control-center are build from the same PKGBUILD, See: https://aur.archlinux.org/pkgbase/asusctl. Since rog-control-center requires libappindicator-gtk3 and supergfxctl they need to be in the make-deps.

kojq commented on 2022-12-04 18:50 (UTC)

@fabiscafe I was thinking based on what I read that these dependencies can be removed:

  • libappindicator-gtk3 (libappindicator-bzr) (make)
  • supergfxctl (supergfxctl-git, supergfxctl) (make)

I don't try/want to make this something of a supported distribution option.

👌

fabiscafe commented on 2022-12-04 18:07 (UTC)

@kojq I don't quite understand your comment, at least the package splitting section. (Is it just as an information?)

For the last part - to be honest, while I maintain the PKGBUILD I can not verify it as I don't have actual supported hardware (Vivobook). So I don't try/want to make this something of a supported distribution option. ☺️

kojq commented on 2022-12-04 17:27 (UTC)

To quote from a member of the team (with minor corrections):

"rog-control-center has been split out from the asusctl package into a separate package with the same name, rog-control-center. If you want that GUI, please install it; it is not a dependency of asusctl.

This is done to allow users to use asusctl only without pulling supergfxctl and libappindicator-gtk3 to have rog-control-center working."

Also, a personal suggestion is to (maybe) communicate with them about these packages being maintained.

👋

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »