src2pkg doinst.sh auto library links

rpedrica · 04-01-2011, 02:36 PM

Hi Gilbert, quick q re. auto generated doinst.sh files when using the -A switch. The file will contain link removal and generation for libraries in the package eg.

( cd usr/lib64 ; rm -rf libk5crypto.so.3 )
( cd usr/lib64 ; ln -sf libk5crypto.so.3.1 libk5crypto.so.3 )

When upgrading to a new version of the app, the library name might change eg.

libk5crypto.so.4.2

So the links that doinst.sh creates is now incorrect. ie. the link is now dead because it points to a file that does not exist. Does one have to regenerate .src2pkg and resulting doinst.sh when using a new version of the package or is there another way to have doinst.sh regenerated without redoing .src2pkg?

Regards, Robby

tuxdev · 04-01-2011, 05:52 PM

if you build a package for libk5crypto.so.4.2, unless you've overridden doinst.sh autogeneration, you'll end up with

Code:

( cd usr/lib64 ; rm -rf libk5crypto.so.4 )
( cd usr/lib64 ; ln -sf libk5crypto.so.4.2 libk5crypto.so.4 )

Yes, anything that uses the old library will no longer work, but that's by design. The "major version" changed from 3 to 4, which means the developer of the library did something that was not backwards-compatible. You can generally force the issue by creating the libk5crypto.so.5 link manually, but that has an extremely good chance of causing weird crashes.

TLDR: The doinst.sh is fine, but sometimes it'll leave broken links that don't actually cause a problem.

gnashley · 04-02-2011, 10:02 AM

eah, if the library versions change, then you need a new doinst.sh. You can, of course, manually edit it to achieve that. or, if it was generated completely at first by src2pkg, then just delete it and a new one will be generated. Note that, using '-A' simply means that what was placed in the package gets copied to the current dir. If you don't use '-A', it will still be generated any time it is needed. If you have, or need, to add some static code to the script, then put it in either doinst.prepend and/or doinst.append. I have quite a few done that way so I still have the advantage of auto-generated links creation, along with arbitrary (static) code before or after that. Remember, if you have a doinst.sh or doinst.sh.gz present, then they will be used instead of generating new code.