m. allan noah wrote:
> On Fri, Feb 20, 2009 at 3:08 PM, Chris Bagwell <chris at cnpbagwell.com>
> wrote:
>
>> When backend was converted to automake, it uses the standard automake
>> support to install libraries. That does install symlinks on fresh install.
>>
>> I think your point is that now if a user installs, libsane.so.1.1.0 on top
>> of a previous libsane.so.1.0.19 install then libsane.so symlink still points
>> to libsane.so.1.0.19?
>>
>
> it's not just that it leaves the links behind, it actually makes the
> links to 1.0.19, even when 1.1.0 is also installed.
>
>
>> I've not tried above yet but seems reasonable libtool behavior to me. I'll
>> read up on libtool and see if they have an "opinion" on this.
>>
Couldn't find any documentation related to what libtool behaviour should
be in tihs area.
I just now installed sane 1.0.19 tarball into a private directory and
then installed current CVS on top of it. The behaviour I got seems to
be the behaviour you want. In the end, all symlinks were updated and
pointed to latest so. I had the following in ${prefix}/lib and other
backends followed same behaviour.
libsane.la
libsane.so -> libsane.so.1.1.0
libsane.so.1 -> libsane.so.1.1.0
libsane.so.1.0.19
libsane.so.1.1.0
Let me know if you continue to see different behaviour and we can
continue to debug it.
Also, this means I won't be porting over the Makefile symlink logic I
previously mentioned since it was broke and current libtool seems to be
OK on all platforms I tested.
Chris
