Github messages for voidlinux
 help / color / mirror / Atom feed
From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] create pipewire-session-manager alternative group
Date: Tue, 31 Oct 2023 03:26:06 +0100	[thread overview]
Message-ID: <20231031022606.Oic4WXMsHlDCeNO5rIFkq-7LPVOD6Lw3Qg3LgvY50rE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46960@inbox.vuxu.org>

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

New comment by cinerea0 on void-packages repository

https://github.com/void-linux/void-packages/pull/46960#issuecomment-1786336038

Comment:
Yeah, the conditional execution could work. Here's how I start the pulse server and wireplumber from my user's config directory:

```
context.exec = [
	{ path = "/usr/bin/wireplumber" args = ""
	  condition = [ { exec.session-manager = null } { exec.session-manager = true } ] }
	{ path = "/usr/bin/pipewire" args = "-c pipewire-pulse.conf"
	  condition = [ { exec.pipewire-pulse = null } { exec.pipewire-pulse = true } ] }
]
```

I'd have to test it, but based on how it's documented switching the files to this shouldn't launch wireplumber or the pulse server if they're already running, even if it's the same file getting symlinked multiple times.

  parent reply	other threads:[~2023-10-31  2:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-29 19:11 [PR PATCH] " classabbyamp
2023-10-29 20:07 ` ahesford
2023-10-29 20:08 ` classabbyamp
2023-10-29 20:09 ` [PR PATCH] [Updated] " classabbyamp
2023-10-29 20:35 ` ahesford
2023-10-30 20:02 ` oreo639
2023-10-30 20:03 ` oreo639
2023-10-30 20:05 ` oreo639
2023-10-30 20:06 ` oreo639
2023-10-30 20:28 ` oreo639
2023-10-30 20:30 ` oreo639
2023-10-31  2:26 ` cinerea0 [this message]
2023-10-31  2:46 ` oreo639
2023-10-31  2:46 ` oreo639
2023-11-18 20:57 ` cinerea0
2024-02-17  1:44 ` 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=20231031022606.Oic4WXMsHlDCeNO5rIFkq-7LPVOD6Lw3Qg3LgvY50rE@z \
    --to=cinerea0@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).