Hello!
[Mon, 20 Feb 2006] Mario Lang wrote:
> Package: libjack0.100.0-0
^^^^^^^^^^^^^^^^
> Could you please explain the rationale behind above patch?
> By default, jack uses ${libdir}/jack as directory for searching
If you use ${libdir}/jack, you can't install two different versions
(sonames thus different package names) of libjack at the same time. That
makes Library transitions extra-hard.
> lib version number in it. However, there is no obvious way
> to figure out whats the correct dir to use for addon packages.
The name ist always ${libdir}/${libjack-package-name}. Easy enough?
> So, how would a in-process client module know where
> it has to go on a Debian system? On systems running jackd from
> source, they simply go into /usr/lib/jack, which is relatively
> easy to figure out in configure scripts.
... and clashes for above reason.
> I suggest we either drop the above patch, and use
> the same ADDON_DIR as other jackd installations, or
> we offer some way for addon packages to query this
> directory name.
I assume you already have found a way to depend on a libjack package.
Then the location for the modules is as described above.
Hope that helps.
Robert.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
