From: TeusLollo <TeusLollo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: wireplumber: create /var/lib/wireplumber
Date: Fri, 02 Jun 2023 22:54:22 +0200 [thread overview]
Message-ID: <20230602205422.AybOBSpQANvx4yHQAXyMdMs8o7-VY_hthYZtWDijw3E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44122@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 676 bytes --]
New comment by TeusLollo on void-packages repository
https://github.com/void-linux/void-packages/pull/44122#issuecomment-1574295094
Comment:
Indeed, that's what I was guessing, but I wasn't going to learn Pipewire just to confirm.
EDIT:
I don't suppose there's a way to run a conditional check on the `make_dirs` to see if other Pipewire components are present (They will not if wireplumber was pulled as a dependency, which is the case in which the https://github.com/void-linux/void-packages/issues/44231 error will appear)?
It could be otherwise be left as it is, maybe just echoing that, if an user has not Pipewire installed, such an error is not relevant.
next prev parent reply other threads:[~2023-06-02 20:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 2:27 [PR PATCH] " dkwo
2023-05-28 3:23 ` [PR PATCH] [Merged]: " ahesford
2023-05-28 11:46 ` Duncaen
2023-05-28 11:58 ` Duncaen
2023-05-28 14:17 ` dkwo
2023-06-02 20:43 ` Duncaen
2023-06-02 20:46 ` TeusLollo
2023-06-02 20:54 ` TeusLollo [this message]
2023-06-02 21:00 ` TeusLollo
2023-06-02 21:08 ` dkwo
2023-06-02 21:15 ` Duncaen
2023-06-02 21:24 ` TeusLollo
2023-06-02 22:16 ` ahesford
2023-06-03 13:47 ` dkwo
2023-06-03 16:52 ` ahesford
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=20230602205422.AybOBSpQANvx4yHQAXyMdMs8o7-VY_hthYZtWDijw3E@z \
--to=teuslollo@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).