[LAU] dssi_convolve problem
edogawa at aon.at
Thu Jun 14 16:19:13 EDT 2007
Am Montag, 4. Juni 2007 schrieb Florian Schmidt:
> On Monday 04 June 2007, plutek at infinity.net wrote:
> > SOLVED: just tried jack_convolve, and got complaints about not being able
> > to find libconvolve. took a look in /usr/lib and found that there was only
> > libconvolve.so.0.0.8 with no libconvolve.so.0 symlink. added the symlink,
> > and all is fine.
> > is this a SUSE packaging problem?
> Sounds like it. I mean: even if the install target in the libconvolve Makefile
> is broken [which is actually an option since i have no idea what i'm
> doing ;)], SUSE shuoldn't ship the broken build from it..
It seems a simple but annoying typo in the Packman/SUSE spec file has broken the
"update logic" for this package: on my system i have an older package version
libconvolve-0.0.8-0.pm.1, which doesn`t list /usr/lib/libconvolve.so.0 via rpm -qf
although the file is there (that's a mystery to me, because i am sure i didn't
create such a link myself, maybe a relict from an older version). The
current Packman package is called libconvolve0 (which looks like a typo to me,
especially because the -devel package still is named libconvolve-devel),
and therefore it isn't seen as an update by any package manager... I just posted a
bug report to the package maintainer, should be fixed soon.
Something else i find quite confusing: very many -devel packages from SUSE/Packman
contain the unversioned .so symlink for the package. Maybe I don't understand the
reason for this, but that just doesn't make sense to me... I thought usually only
static libs and header files go to the -devel packages. We (jacklab people) had
to ask the jack packager to move that file to the main package because some
application opened the jack library via this file, which forced the user to
install the jack-devel package, or create the symlink manually, if they could
figure out at all what was going on...
More information about the Linux-audio-user