unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: guix-devel@gnu.org
Subject: building with JACK 2 by default?
Date: Fri, 27 Nov 2020 14:01:32 +0100	[thread overview]
Message-ID: <87tutb6jir.fsf@elephly.net> (raw)

Hi Guix,

the official recommendation of the JACK developers used to be to use
whatever JACK version you want as they are compatible anyway and can be
swapped out as needed.  This has now changed and JACK 2 is the only
variant that is under active development.  JACK 1 is in bugfix-only
mode.  See:

  https://github.com/jackaudio/jackaudio.github.com/wiki/Differences-between-jack1-and-jack2

The question is whether we should now build everything with JACK 2
instead of JACK 1.  People like me who still want to use JACK 1
(e.g. because of built-in ALSA MIDI support and support for more than
one soundcard) could simply set LD_LIBRARY_PATH to load the JACK 1
libraries.

We already need to use JACK 2 for some packages which simply won’t build
with JACK 1.  While it may be possible to patch them to accept JACK 1,
which provides almost exactly the same API, I think the more reasonable
approach would be to compromise on JACK 2 for everything.

The downside to building with JACK 2 by default is an increased package
closure due to the larger feature set of JACK 2 (e.g. DBus support).
The upside is that only one version of JACK will be used throughout the
system (we can no longer achieve this with JACK 1, see above) and that
Guix will default to using the recommended version of JACK.

What are your thoughts on this?

-- 
Ricardo


             reply	other threads:[~2020-11-27 12:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27 13:01 Ricardo Wurmus [this message]
2020-12-05 14:16 ` building with JACK 2 by default? Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tutb6jir.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).