Github messages for voidlinux
 help / color / mirror / Atom feed
From: Animeshz <Animeshz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] wireplumber: export $XDG_STATE_HOME to a persistent location
Date: Tue, 12 Apr 2022 04:06:18 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36650@inbox.vuxu.org> (raw)

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

There is a new pull request by Animeshz against master on the void-packages repository

https://github.com/Animeshz/void-packages wireplumber
https://github.com/void-linux/void-packages/pull/36650

wireplumber: export $XDG_STATE_HOME to a persistent location
#### Testing the changes
- I tested the changes in this PR: **YES**|**briefly**|**NO**

In #36416 I've exported HOME to `/var/run/pipewire` but that directory gets recreated every reboot, it was able to persist volume and other configurations when the service restarts but not across system reboots.

`wireplumber` stores the state configuration in `${XDG_STATE_HOME:-$HOME/.local/state}/wireplumber`. I recently also found, `pipewire-media-session` (the builtin media router) utilized `/var/lib/pipewire` as well to persist its state across reboot. So this simply changes the export to do the same.

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

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

From c8170b3e173e6523adc90446a94bdd4334c3f4d6 Mon Sep 17 00:00:00 2001
From: Animesh Sahu <animeshsahu19@yahoo.com>
Date: Tue, 12 Apr 2022 06:49:28 +0530
Subject: [PATCH] wireplumber: export $XDG_STATE_HOME to persistent location

---
 srcpkgs/wireplumber/files/wireplumber/run | 2 +-
 srcpkgs/wireplumber/template              | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/wireplumber/files/wireplumber/run b/srcpkgs/wireplumber/files/wireplumber/run
index ae0cf99e200b..9a28ecdbe9a4 100644
--- a/srcpkgs/wireplumber/files/wireplumber/run
+++ b/srcpkgs/wireplumber/files/wireplumber/run
@@ -6,5 +6,5 @@ sv check dbus >/dev/null 2>&1 || exit 1
 
 exec 2>&1
 
-export HOME=/var/run/pipewire
+export XDG_STATE_HOME=/var/lib/pipewire
 exec chpst -u _pipewire:_pipewire:audio:video -P dbus-run-session wireplumber
diff --git a/srcpkgs/wireplumber/template b/srcpkgs/wireplumber/template
index acbffa27fd8c..5d2d815d98d6 100644
--- a/srcpkgs/wireplumber/template
+++ b/srcpkgs/wireplumber/template
@@ -1,7 +1,7 @@
 # Template file for 'wireplumber'
 pkgname=wireplumber
 version=0.4.9
-revision=1
+revision=2
 build_style=meson
 build_helper=gir
 configure_args="-Dintrospection=enabled -Dsystem-lua=true"

             reply	other threads:[~2022-04-12  2:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12  2:06 Animeshz [this message]
2022-05-13 13:36 ` [PR PATCH] [Closed]: " ericonr
2022-05-13 13:36 ` ericonr

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36650@inbox.vuxu.org \
    --to=animeshz@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).