FS#69913 - [njconnect] switch dependency from jack to libjack.so

Attached to Project: Community Packages
Opened by tinywrkb (tinywrkb) - Monday, 08 March 2021, 11:50 GMT
Last edited by David Runge (dvzrv) - Friday, 26 March 2021, 17:39 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Some of us switched to PipeWire that now is not dependent at all on JACK (JACK SPA module was disabled), and provides its own libjack.so implementation that is directly using PipeWire daemon instead of the JACK daemon.

The AUR package pipewire-jack-dropin provides libjack.so by using ld.so config to preload the lib and use it instead of JACK/JACK2's libjack.so.


I briefly went through the code and it seems like njconnect only depends on libjack.so and not even using the utilities packaged in jack/jack2 packages so it should be safe to switch the depends from jack to libjack.so like it's done in other packages.
This task depends upon

Closed by  David Runge (dvzrv)
Friday, 26 March 2021, 17:39 GMT
Reason for closing:  Won't fix
Additional comments about closing:  The AUR is not supported.
Comment by David Runge (dvzrv) - Friday, 26 March 2021, 17:39 GMT
@tinywrkb: Thanks for the report.

Please note, that the AUR is not supported.
As such, the dependency on jack is correct and if the package in the AUR aims at replacing jack/jack2 it must conflicts/provides/replaces jack.

Once I get around to upgrading/ rebuilding njconnect I will update the package to (also) depend on libjack.so though!

Loading...