Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#71063 - [pipewire-jack] pipewire-jack should provide jack and libjack.so=0-64
Attached to Project:
Arch Linux
Opened by Thomas Girod (tgirod) - Sunday, 30 May 2021, 20:50 GMT
Last edited by David Runge (dvzrv) - Sunday, 16 January 2022, 14:53 GMT
Opened by Thomas Girod (tgirod) - Sunday, 30 May 2021, 20:50 GMT
Last edited by David Runge (dvzrv) - Sunday, 16 January 2022, 14:53 GMT
|
Detailspipewire as a dropin alternative is getting more and more interesting - it would make sense for it to provide jack and libjack.so=0-64 so one can install many pro-audio packages without pulling jack as a dependency.
|
This task depends upon
Closed by David Runge (dvzrv)
Sunday, 16 January 2022, 14:53 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with pipewire-jack >= 1:0.3.43-2
Sunday, 16 January 2022, 14:53 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with pipewire-jack >= 1:0.3.43-2
See https://wiki.archlinux.org/title/PipeWire#JACK_clients
Actually using this dependency provider would simply break every program trying to link to libjack...
https://man.archlinux.org/man/pw-jack.1
Apparently it is possible to install as the system jack implementation too, which I think is what you actually wanted.
While this setup is not super common but affects pro-audio devices, I would be much more happy with a solution that still allows both use-cases.
An intermediate package that introduces the required symlinks or modifies ld.so.conf (similar to how it is done in pipewire-jack-dropin [1]) and conflicts/provides/replaces jack would be much more flexible for the time being, as it will take some time for things to be fully compatible (if at all possible e.g. via ALSA drivers). The current setup allows people to check for compatibility or even attempt a hybrid setup, while still relying on jackd, which is able to use the FFADO driver stack.
[1] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=pipewire-dropin
I have created a new upstream project [1] which will allow us to devendor the existing tooling from jack1 and jack2. The effort is tracked in a ticket [2].
Afterwards I will change the pipewire build to have pipewire-jack provide jack.
[1] https://github.com/jackaudio/jack-example-tools/
[2] https://github.com/jackaudio/jack-example-tools/issues/9