For jack-audio-connection-kist to go in, assuming nothing is removed, a lot
of stuff *still* has to happen first.
I'm going to draw this as a dependency tree, where under each item
are the items which need to happen first.
==> hint jack-audio-connection-kit/0.75.0-2 alsa-lib/0.9.8-2 ladcca/0.4.0-1
==> Build gem 0.87cvs20031021-1.1 on all arches
==> Build linux-kernel-headers on alpha, hppa, ia64, s390
==> Get puredata 0.37.cvs-10/s390 (built) into the pool
==> Build ecasound2.2/2.3.1-1 on arm, sparc, m68k, s390
==> Get python2.3/2.3.3-4 compiled on arm, sparc, m68k, s390
==> Fix fftw3 build bug #225960
----
If you want to get jack-audio-connection-kit in *today*, on the other hand,
I believe you have to do the following. I checked and there don't seem to be
any packages depending on the packages I suggest removing, so this should work.
# This needs new linux-kernel-headers before building.
remove gem/0.87-5.2
# These two depend on ecasound2.2, which waits for python2.3.
remove ecamegapedal/0.4.1-3
remove ecawave/1:0.6.0-6
# This depends on fftw3, which still needs work
remove freqtweak/0.4.8-1
# It looks like if these three libraries go in, everything else
# will become installable, even puredata and pd-externals.
hint jack-audio-connection-kit/0.75.0-2 alsa-lib/0.9.8-2 ladcca/0.4.0-1
This is almost certainly worth it, given the sheer number of packages
waiting for alsa-lib and jack-audio-connection-kit (including significant
parts of GNOME and KDE).
--
Nathanael Nerode <neroden at gcc.gnu.org>
http://home.twcny.rr.com/nerode/neroden/fdl.html
