From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] pipewire: can't load api.bluez5.enum.dbus: No such file or directory
Date: Sun, 21 Mar 2021 13:16:29 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29655@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
New issue by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/issues/29655
Description:
I'm opening this one because I realized our packaging is wrong wrt pipewire and bluetooth. This error should not be there.
This is upstream default policy:
```
with-pulseaudio = [
with-audio
bluez5
restore-stream
streams-follow-default
]
```
which means: load the bluetooth plugin when pulseaudio functionality is installed, and we install pulseaudio functionality by default.
Two possibilities:
1) Stay with upstream policy and add `libspa-bluetooth` to `depends`. This however adds unwanted dependencies for users not using bluetooth.
2) Change the policy (it should be fine as a distro) into:
```
with-bluetooth = [
bluez5
]
with-pulseaudio = [
with-audio
restore-stream
streams-follow-default
]
```
And provide an additional package `pipewire-bluetooth` that install the bluetooth plugin and the `with-bluetooth` file. I could try to propose this policy to upstream, if it's a good idea.
[3) For now, simply wait for configuration to stabilize, since things could change?]
Related: #29570
cc @ericonr
next reply other threads:[~2021-03-21 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 12:16 st3r4g [this message]
2021-04-09 10:32 ` st3r4g
2021-04-09 15:04 ` [ISSUE] [CLOSED] " 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-29655@inbox.vuxu.org \
--to=st3r4g@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).