On Wed, 2007-04-18 at 10:33 -0500, Josh Lawrence wrote: This is how I do it: 1. Install the latest Debian package (using 'apt-get install libjack0.100.0-0') 2. Get the JACK source package you need, configure it with --prefix=/usr, build it and install it (without uninstalling the Debian package) 3. Remove all files starting with libjack-0.100.0 in /usr/lib 4. Create a symbolic link: /usr/lib/libjack-0.100.0.so.0 -> /usr/lib/libjack.so Done. Now old JACK programs from Debian packages should work (since the database thinks that the JACK packages are still installed, although they really have been overwritten) and programs requiring the newer API (MIDI etc) should also work. If the libjack ABI ever becomes incompatible with the old one your Debian packaged JACK clients may start acting weird though. Also, your JACK-from-source installation will be overwritten if you do apt-get upgrade and there are newer JACK packages than the one you have installed. But all you have to do then is to reinstall your source build.

There are probably cleaner ways to do this (like copying over the debian subdirectory from a Debian source package to your new tarball and build a proper Debian package), but this works reasonably well for me.

there must be some way in debian to say, "don't worry about the jackd dependency, I've already got that installed." or am I doomed to compile everything from source now that I've compiled jack from source? is it all or nothing?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Apr 18, 2007 at 11:57:14AM -0400, Lee Revell wrote: This issue has me stuck right now too. I need jack 103 and also I want to try jackdmp again too. The debian packages for jack 101 and jack 102 are really weird. Either they weren't done correctly, or my debian knowlege is not up-to-date with the latest hip and happenin' tools. I have successfully built, backported, and/or upgraded packages for several audio apps for Etch (http://www.restivo.org/projects/debian/various-etch-audio-backports/). But jackd has not given me any success and tomorrow I think I'll have to focus on it and try to get it working. It's "in my critical path" since jack 102 and freebob 1.0.3 are inoperative on my Core 2 Duo. If the version you want is already in testing or unstable but didn't make it into Etch, it's pretty simple. Just get the original source, diff file, an dsc file by going to http://pacakges.debian.org, then: dpkg-source -x $the_dsc_file cd $source_subdir debuild -uc -us Updating packages to a version that isn't yet in debian (not even unstable), is really easy. I did this with freebob. wget $orignal_source_for_version_not_yet_in_debian apt-get source $old_package cd $source_subdir uupdate ../$orignal_source_for_version_not_yet_in_debian cd ../$new_source_dir (uupdate will tell you its name) debuild -uc -us Alas, none of the above have worked for JACK. Whatever tool is being used complains about not being able to apply patches. Someone already posted the dh_make tricks to add a package that isn't in debian at all. I find it's a little bit harder than that, but not much. I may try making a whole new package from scratch for JACK and jackdmp, and see how that goes. - -ken