[csw-maintainers] Symlinks to shared libraries

[Maciej (Matchek) Blizinski]

On Wed, Nov 25, 2009 at 11:43 AM, James Lee <james at opencsw.org> wrote:
> On 25/11/09, 10:43:11, Maciej "(Matchek)" Blizinski <maciej at opencsw.org>
> wrote regarding [csw-maintainers] Symlinks to shared libraries:
>
>> I just got a review of my NSPR build from a NSPR/NSS developer,
>> Wan-Teh Chang.  One of the comments was to stop creating a symlink to
>> a shared library.  By default, nspr creates bare *.so files.  My build
>> script renamed them to *.so.$(MINOR_VERSION) and created symlinks from
>> *.so to *.so.$(MINOR_VERSION).
>
>>  > ls -l /opt/csw/lib/nspr/libnspr4.so*
>> lrwxrwxrwx   1 root     other         13 Nov 23 23:46
>> /opt/csw/lib/nspr/libnspr4.so -> libnspr4.so.8
>> -rwxr-xr-x   1 root     bin       324344 Nov 23 23:02
>> /opt/csw/lib/nspr/libnspr4.so.8
>
>> Do we have any policy which requires creating symlinks?
>
> It's not about CSW policy but how ld and ld.so.1 work and versioning.
> What's the SONAME?

$ /.SUNWnative/usr/sfw/bin/gobjdump -p
work/solaris8-sparc/install-isa-sparcv8/opt/csw/lib/libnspr4.so.8  |
grep SONAME
  SONAME      libnspr4.so

This means applications will be linked against libnspr4.so no matter
which is the symlink and which is the regular file, right?

Maciej