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#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
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
|
DetailsI 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
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