Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libjack-dev vs libjack-jackd2-dev #39

Open
musodojo opened this issue Jul 19, 2022 · 4 comments
Open

libjack-dev vs libjack-jackd2-dev #39

musodojo opened this issue Jul 19, 2022 · 4 comments
Labels
question Further information is requested

Comments

@musodojo
Copy link

In the Install section, you say "The dependencies are: ..." and include "libjack-dev".

Installing "libjack-dev" on my Ubuntu Studio causes the apt package manager to uninstall other packages including studio-controls.

I can avoid this by installing "libjack-jackd2-dev" instead and everything compiles as expected with no packages needing to be removed.

@Stazed
Copy link
Owner

Stazed commented Jul 19, 2022

The difference is jack1 vs jack2. They should be interchangeable. I believe that jack1 is no longer being developed. Ubuntu Studio defaults to using jack2. The dependencies list is somewhat generic since different distros use different naming conventions.

@Stazed Stazed added the question Further information is requested label Nov 10, 2022
@domichel
Copy link

domichel commented Oct 6, 2023

On gentoo, jack is a virtual dependency, which in turn depend on one of jack1 or jack2 and exclude the other one, the choice being an user choice. The main difference being than jack1 is mostly used on uni-processor machines, when jack2 is mostly used on multi-processor x86-64 machines. Jack1 is in maintenance only mode, so the real alternative of today is much more between jack2 and pipewire, both of them being actively developed, jack2 in order to be safe, pipewire for the brave.

@domichel
Copy link

domichel commented Oct 6, 2023

I just took a look into the virtual/jack ebuild, they added pipewire into it, so it is now one of jack1, jack2 or pipewire, and only one of them. That system imply that all jackified packages will depend only on that virtual, and that to shift from one to another jack implementation must be as painful than editing 2 lines into a config file and making a system update.

@domichel
Copy link

domichel commented Oct 6, 2023

And sorry for my English, I am never sure if I make the good choice between than and that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants