[Mono-dev] dependency conflicts on rpm based distros
vogt at itwm.fraunhofer.de
Thu Jul 23 06:21:34 EDT 2009
Andrew Jorgensen wrote:
> Hi Martin,
> If mono-find-requires says that 126.96.36.199 is required that's really what is required and 188.8.131.52 will not work.
Should banshee-1 crash?
Despite the fact that banshee-1 may not the appropiate example,
because it almost does not run at all for me (with taglib-sharp-184.108.40.206
and taglib-sharp-220.127.116.11) I can start it without a crash.
And at least it opens the dll:
>vogt[~]>lsof -p 6106 | grep taglib-sharp
>banshee-1 6106 vogt mem REG 253,1 287744 1134919
6106 is the pid of banshee.
I looked an the configure.ac for taglib-sharp:
AM_INIT_AUTOMAKE([1.9 dist-bzip2 tar-ustar])
But the question is, does the find-requires script follows the
recommended quidelines for mono library versioning or not?
I dont know much about mono and its internal libs/versions, but the
find-requires script return "mono(taglib-sharp) = 18.104.22.168"
Is this meant to be the <major>.<minor>.<build>.<revision> from a
If it is, then the common practice is, that a lib is compatible
if only "<build>.<revision>" changes.
RPM cannot handle this.
> There are certainly problems with the mono-find-* scripts but that is not one of them.
> You could verify what I'm saying by manually installing banshee
> using the --nodeps option passed to rpm. You will find that banshee
> will not run properly without the correct version of taglib-sharp.
More information about the Mono-devel-list