#903 Symlinks for back level support gone from 4.0.1

v4.0.1
closed
5
2012-08-14
2010-04-14
mdlueck
No

I am working with Mark Miesfeld to test v4.0.1.5779 and have run into a show-stopper bug. Used to be that symlinks for "DLL's" compiled with older versions of ORexx / ooRexx were maintained pointing to the current library. These seem to be gone.

Specifically I am trying to run something compiled against ORexx 2.x for Linux. Should be something like...

librexxapi.so.2 -> /opt/ooRexx/lib/ooRexx/librexxapi.so.4.0.0

and I do not see any such legacy symlinks in the 4.0.1 build.

Please fix, send me another test build please. Thanks! :-)

Discussion

  • Mark Miesfeld

    Mark Miesfeld - 2010-04-14

    Hmm ... I forgot that the Debian scripts need to be manually updated. I do that from the rpm spec.

     
  • Mark Miesfeld

    Mark Miesfeld - 2010-04-14

    Well, I take that back, sort of. The script looks correct to me.

    Michael did you see this in the official 4.0.1 beta 1 build also?

     
  • Mark Miesfeld

    Mark Miesfeld - 2010-04-14

    Committed revision 5781.

    Fixed in 4.0.1, I still need to fix trunk.

     
  • mdlueck

    mdlueck - 2010-04-15

    All I have looked at for testing is the ooRexx/oorexx-4.0.1.5779.i586.deb you sent to me.

    I tried updating our server to the new build, and ran into the missing symlinks.

    I can not keep track of where you keep the official Debian build scripts... the place I knew of I seem to recall you say is the "old spot" and I have not figured out where the current spot in svn is. I would think svn must have gotten regressed or something? How else could the symlink creation script end up missing links? I would think you just add more scripts, never delete links created by prior package versions.

    Seems you corrected something. Please let me know when there is a new package to test out.

     
  • mdlueck

    mdlueck - 2010-04-21

    Fix confirmed with ooRexx-4.0.1.i586.rc1.deb

    Thanks much! Looking good!

     
  • Mark Miesfeld

    Mark Miesfeld - 2010-09-08

    The fix for this item was in the 4.0.1 release.

     


Anonymous

Cancel  Add attachments