Robert Jordens <[EMAIL PROTECTED]> writes:
> 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?No. How would a program compiled from source know which name the Debian package for jack has? $ pkg-config --variable=libdir jack /usr/lib How would you proceed from there? Maybe we could just add addondir to the jack.pc? >> 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. OTOH, I really dont think any serious jack user has two versions running at the same time. But I see your above point of course. > >> 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. I am not talking about packaged software, I am talking about a source tarball being installed by a user on a debian system using jack. -- CYa, Mario
pgprLeCaHzeVk.pgp
Description: PGP signature
