You are not logged in.
Hello.
I just adopted the jack-audio-connection-kit-dbus package and am contacting the current maintainers of jack-audio-connection-kit-mp and jack-audio-connection-kit-svn to suggest the following minor enhancements.
Renaming -- by uploading a new package and asking for removal of the old one -- consistently with the jack package in extra, this is the scheme I'm proposing:
jack-audio-connection-kit-dbus → jack-dbus (or alternatively jackdbus)
jack-audio-connection-kit-mp → jack2 (or alternatively jackmp)
jack-audio-connection-kit-svn → jack-svn
Adding the line
provides=('jackdbus')to Jack PKGBUILDs using the --dbus option, to ease the job of those who maintain any package depending on the `jackdbus` executable.
What are the community thoughts (especially the Pro Audio people' ones) on this?
Cheers.
Offline
Correct if I am wrong here, but I thought Jack2 and Jack with dbus were one in the same?
Did dbus support get moved to jack1?
Offline
No, jackdmp (jack2) and jack are alternative implementations of jack. Both come in 'classic' versions and 'dbus' versions. jackdmp defaults to dbus, since its developer prefers that. Jack defaults to classic (run a single executable with switches), but can be run using the dbus control mechanism created by jack2's developer.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline