Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidbert <voidbert@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: cpupower-gui-1.0.0
Date: Mon, 07 Aug 2023 00:31:50 +0200	[thread overview]
Message-ID: <20230806223150.TpMsHg5NolNYUsomCsBFSuh4GO6T_zxGi7YmpYXDGWY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45355@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]

There is an updated pull request by voidbert against master on the void-packages repository

https://github.com/voidbert/void-packages cpupower-gui
https://github.com/void-linux/void-packages/pull/45355

New package: cpupower-gui-1.0.0
#### Testing the changes
- I tested the changes in this PR: **YES**

#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**

Addresses issue #45182.

#### Local build testing
- I built this PR locally for my native architecture, (x86_64-musl)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - x86_64
  - i686
  - armv6l
  - armv6l-musl

#### Help wanted

##### Polkit testing

I'm having lots of trouble getting an authentication agent working in my sway WM system. I would thank anyone that uses a DE (or got polkit working in a WM) to test if they can set CPU frequencies from a regular user, without having to launch the whole app as root.

##### Runit services

I already wrote a runit service but I keep getting the following error:
```
# sv once cpupower-gui
warning: cpupower-gui: unable to open supervise/ok: file does not exist
```
I can confirm that `/var/service/cpupower-gui/supervise` is a broken symlink, even after rebooting the system. After a reboot, the service doesn't produce any effects on the CPU frequencies, so I think it's not being started.

However, `runsv` seems to work, after which I start getting a different error:
```
# sv once cpupower-gui
fail: cpupower-gui: runsv not running
```

Does anyone more knowledgeable in runit know how I can fix this? Also, I think there's no great way to port user services from systemd, but again, I'd be happy anyone more informed would be willing to help.


A patch file from https://github.com/void-linux/void-packages/pull/45355.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cpupower-gui-45355.patch --]
[-- Type: text/x-diff, Size: 2383 bytes --]

From da025ae9b16f22a7a69f2583d69c256d2aa260fa Mon Sep 17 00:00:00 2001
From: voidbert <humbertogilgomes@protonmail.com>
Date: Mon, 31 Jul 2023 15:41:26 +0100
Subject: [PATCH] New package: cpupower-gui-1.0.0

---
 srcpkgs/cpupower-gui/files/cpupower-gui/run |  3 +++
 srcpkgs/cpupower-gui/patches/meson.patch    | 12 ++++++++++++
 srcpkgs/cpupower-gui/template               | 17 +++++++++++++++++
 3 files changed, 32 insertions(+)
 create mode 100644 srcpkgs/cpupower-gui/files/cpupower-gui/run
 create mode 100644 srcpkgs/cpupower-gui/patches/meson.patch
 create mode 100644 srcpkgs/cpupower-gui/template

diff --git a/srcpkgs/cpupower-gui/files/cpupower-gui/run b/srcpkgs/cpupower-gui/files/cpupower-gui/run
new file mode 100644
index 0000000000000..50801bb9389a7
--- /dev/null
+++ b/srcpkgs/cpupower-gui/files/cpupower-gui/run
@@ -0,0 +1,3 @@
+#!/bin/sh
+/usr/bin/cpupower-gui config
+sv down cpupower-gui
diff --git a/srcpkgs/cpupower-gui/patches/meson.patch b/srcpkgs/cpupower-gui/patches/meson.patch
new file mode 100644
index 0000000000000..2fb01efa63ee3
--- /dev/null
+++ b/srcpkgs/cpupower-gui/patches/meson.patch
@@ -0,0 +1,12 @@
+diff --git a/data/meson.build b/data/meson.build
+index 4dbfe5c..3be1e44 100644
+--- a/data/meson.build
++++ b/data/meson.build
+@@ -12,7 +12,6 @@ desktop_conf = configuration_data()
+ desktop_conf.set('icon', application_id)
+ 
+ desktop_file = i18n.merge_file(
+-  'desktop',
+    input: configure_file(
+     input: files('org.rnd2.cpupower_gui.desktop.in.in'),
+     output: 'org.rnd2.cpupower_gui.desktop.in',
diff --git a/srcpkgs/cpupower-gui/template b/srcpkgs/cpupower-gui/template
new file mode 100644
index 0000000000000..b7079d427433d
--- /dev/null
+++ b/srcpkgs/cpupower-gui/template
@@ -0,0 +1,17 @@
+# Template file for 'cpupower-gui'
+pkgname=cpupower-gui
+version=1.0.0
+revision=1
+build_style=meson
+hostmakedepends="pkg-config glib-devel gettext"
+depends="glib python gtk+3 polkit python3-dbus python3-gobject python3-xdg libhandy1"
+short_desc="GUI for changing CPU frequency limits"
+maintainer="voidbert <humbertogilgomes@protonmail.com>"
+license="GPL-3.0-or-later"
+homepage="https://github.com/vagnum08/cpupower-gui"
+distfiles="https://github.com/vagnum08/cpupower-gui/archive/v${version}.tar.gz"
+checksum=09f8b9619e974abe00fc06c0d5528b6a36518f6b283b3db338349bada1d51492
+
+post_install() {
+	vsv cpupower-gui
+}

  parent reply	other threads:[~2023-08-06 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 15:28 [PR PATCH] " voidbert
2023-07-31 15:34 ` [PR PATCH] [Updated] " voidbert
2023-08-06 22:31 ` voidbert [this message]
2023-08-07 11:17 ` voidbert
2023-11-06  1:46 ` github-actions
2023-11-20  1:46 ` [PR PATCH] [Closed]: " github-actions

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230806223150.TpMsHg5NolNYUsomCsBFSuh4GO6T_zxGi7YmpYXDGWY@z \
    --to=voidbert@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).