Package Details: rog-control-center 5.0.10-0.3

Git Clone URL: (read-only, click to copy)
Package Base: asusctl
Description: App to control asusctl
Upstream URL:
Keywords: anime asus matrix rog
Licenses: MPL-2.0
Submitter: fabiscafe
Maintainer: fabiscafe
Last Packager: fabiscafe
Votes: 15
Popularity: 1.91
First Submitted: 2021-09-18 11:01 (UTC)
Last Updated: 2024-04-01 20:52 (UTC)

Pinned Comments

fabiscafe commented on 2023-06-13 21:53 (UTC)

Merge/Pull Requests / Bugreports

Latest Comments

1 2 3 4 5 Next › Last »

fabiscafe commented on 2024-04-02 21:33 (UTC)

@labaman In case someone imports it to Arch it can be pushed with pkgrel of 1 instead of 2

labaman commented on 2024-04-02 06:58 (UTC)

Can you tell me why to use fractional $pkgrel?

redsolja commented on 2024-03-18 20:12 (UTC)

@fabiscafe: worked! Thanks! Any idea how to not need such an environment? I mean, I haven't changed anything at mine at all. How to "reset" it to a clean one that is clean by default?

yochananmarqos commented on 2024-03-14 00:06 (UTC)

@fabiscafe: Yes, the old libappindicator; i.e., libappindicator-gtk3 / libappindicator-gtk2 hasn't seen a release since 2017. Since I do a lot of packaging, I've noticed many projects are switching to libayatana-appindicator. There's still a transition with a fallback in some cases. In this case, ASUS uses libappindicator and libappindicator-sys crates built into the binary. I just noticed that the Ubuntu dependencies mentioned libayatana-appindicator3-1, so apparently that will work now with ROG Control Center.

fabiscafe commented on 2024-03-13 23:19 (UTC)

@yochananmarqos Is there any benefit to use libayatana-appindicator over libappinticator?

yochananmarqos commented on 2024-03-13 20:44 (UTC)

@fabiscafe: It seems upstream supports libayatana-appindicator now. See the README

fabiscafe commented on 2024-03-13 09:21 (UTC)

@yochananmarqos Nice catch! This will be adopted :D

yochananmarqos commented on 2024-03-12 21:01 (UTC)

@fabiscafe: The export is in Rust package guidelines for a reason. ;)

ngoquang2708 commented on 2024-03-12 15:49 (UTC)

Setting CARGO_TARGET_DIR=target is just reset everything back to default value. Anyway, we are already modified CARGO_HOME.

fabiscafe commented on 2024-03-12 15:12 (UTC)

@ngoquang2708 Would you report this upstream? I don't want to workaround an upstream issue caused by a user setting. Because the supported scope of this PKGBUILD is to be build in a clean build environment. 😟