Package Base Details: asusctl

Git Clone URL: https://aur.archlinux.org/asusctl.git (read-only, click to copy)
Keywords: anime asus matrix rog
Submitter: fabiscafe
Maintainer: fabiscafe
Last Packager: fabiscafe
Votes: 15
Popularity: 1.41
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

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

Latest Comments

1 2 3 4 5 6 Next › Last »

fabiscafe commented on 2024-05-04 19:16 (UTC)

@callegar Yes. The 'SKIP' was just needed because we didn't had checksum support for VCS source, that we have now with pacman 6.1

callegar commented on 2024-05-04 06:33 (UTC)

Should these two items actually go together as they do now in the PKGBUILD?

source=("git+https://gitlab.com/asus-linux/asusctl.git#tag=$pkgver")
b2sums=('2be7cd61489d223e511e71c8d62b4f68903a6efed98848491d7824cceb87e4cd3c90db015c1159020ec493aa088472572549126ac36349c475098ded0842fe88')

I am getting a checksum validation error, with a notice that there is no asusctl to check. Guess this is because rather than downloading an archive (single file), the git+https protocol ends up directly in an expanded source tree via git.

Apparently https://wiki.archlinux.org/title/VCS_package_guidelines suggests that when sources are obtained from a VCS, the sums should be set to SKIP. This is not so clear to me though, because the general case where sources are derived from a VCS is the case of getting a branch tip, while here a tagged tree is targeted that is static rather than dynamic.

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. ;)

1 2 3 4 5 6 Next › Last »