Re: libkpathsea3 incompatibility problem

[Olaf Weber <olaf@infovore.xs4all.nl>]

Julian Gilbey writes:
> On Wed, Feb 19, 2003 at 07:02:26PM +0100, Olaf Weber wrote:

>> Perhaps I should add a few notes on what upstream thinks it's doing.
>> [...]

> Thanks for this info, Olaf.  So maybe the best temporary solution
> until kpathsea is really supported as a shared library is to only
> ever compile it into software statically?

Actually, I don't expect many changes in the current kpathsea until it
gets replaced (by the middle of this year, if I make my schedule).  So
if you wish to continue the current situation you should be fairly
safe.

For kpathsea, the current sources use libtool -version=4:0:0 which
results in an soname of libkpathsea.so.4 (but on IRIX apparently of
libkpathsea.so.5 -- I can't say I'm actually thrilled with the way
libtool's versioning works).  The version was chosen because you have
to pick something, and this seemed a not unreasonable choice.  If it
would impose hardship the number can be changed before an actual
release is cut.

-- 
Olaf Weber

               (This space left blank for technical reasons.)