Closed andreasstieger closed 8 months ago
Yes, this one's intentional. The idea is that you can write programs using '#include "libUseful-5"', but if for some reason you wanted to be specific, maybe there's a feature that only exists in libUseful-5.9 or something, then you can specify the exact version.
I could maybe add an autoconf option to turn this on/off though?
This.. is not how this is done for shared libraries. You could use feature flags that the consuming code could check for, or just look at the version macro. In other words, unless "5" and "5.9" are sonames it does not seem to make a lot of sense.
What about a symlink from libUseful-5.9 to libUseful-5, would that work? It's just that way you can build against one version, or the other, as desired, just by changing #include and -lUseful-
That works. In fact this this is what %fdupes
does in the spec (hardlinks in this case but this is not relevant)
Okay, I'll set that up for the next release, and look into the soname thing. It'll take a few days due to other commitments right now.
done using symlinks.
The header files seem to be installed twice: