FS#53583 - [jack2] unnecessary dbus-only build/split package?

Attached to Project: Community Packages
Opened by Tom Yan (tom.ty89) - Thursday, 06 April 2017, 03:05 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 05 May 2017, 17:17 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To Ray Rashif (schivmeister)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I notice that the jack2 package is actually a classic/dbus mixed build, which means it provides the same dbus interaction functionality as jack2-dbus does, and additionally provides jackd. So what is the point of the dbus-only build/split package? What circumstances would make us hate jackd so much that we would want to provide such variant? If there should be a dbus-only build, why not a classic-only build as well?
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 05 May 2017, 17:17 GMT
Reason for closing:  Not a bug
Comment by Ray Rashif (schivmeister) - Wednesday, 26 April 2017, 19:37 GMT
I wrote a post about this several years ago on ArchAudio.org, which has gone the way of the Dodo. [0] One of the main sources of documentation can now be found at https://github.com/jackaudio/jackaudio.github.com/wiki/JackDbusPackaging

In short, the mixed mode is a compromise but is primarily meant to be used as a "classic" version (in our case at least), with the _option_ for using d-bus. The dbus-only build could potentially be used in systems where user experience is more important. According to the stats, [1] jack2-dbus is indeed used by some, and I hazard a guess that it's mostly systems with PulseAudio.

[0] http://web.archive.org/web/20111012202319/http://archaudio.org:80/2010/10/arch-linux-new-audio-packages-including-jack2/
[1] https://www.archlinux.de/?page=PackageStatistics

Loading...