Project

Profile

Help

Bug #4178

License file not found with symbolic links

Added by O'Neil Delpratt over 1 year ago. Updated 10 months ago.

Status:
In Progress
Priority:
Normal
Category:
Linux
Start date:
2019-03-25
Due date:
% Done:

0%

Estimated time:
Found in version:
1.1.2
Fixed in version:

Description

Reported by user:

There's a bit of inconsistency over how co-locating the licence file and libsaxoneec.so works when used with softlinks.

Soft linking libraries is pretty typical in /usr/lib so I think Saxon should support this.

If I have the below setup in /usr/lib it doesn't work:

lrwxrwxrwx 1 root root 43 Mar 21 22:27 /usr/lib/libsaxoneec.so -> /opt/Saxonica/Saxon-EEC1.1.2/libsaxoneec.so
lrwxrwxrwx 1 root root 31 Oct 16 14:53 /usr/lib/saxon-license.lic -> /opt/Saxonica/saxon-license.lic

Guessing that the softlink for libsaxoneec.so is resolved to it's real path I tried putting saxon-licence.lic in the same directory, but it doesn't work either:

/opt/Saxonica/Saxon-EEC1.1.2/

Some sort of resolving required.

History

#1 Updated by O'Neil Delpratt 10 months ago

  • Status changed from New to In Progress

I am revisiting this bug issue to provide a better solution.

As a workaround users with a license can request to activate the product via C++ API. We would send users a small C++ class to activate the product.

#2 Updated by O'Neil Delpratt 10 months ago

Another workaround would be to use the licenseFileLocation configuration property:

  $saxonProc = new Saxon\SaxonProcessor(true);
  $saxonProc->setConfigurationProperty("http://saxon.sf.net/feature/licenseFileLocation", "/usr/lib/saxon-license.lic");

Please register to edit this issue

Also available in: Atom PDF