Won't this change break systems which don't have libpcsclite.so.1?
Changes like this need to be thought through. What happens when
libpcsclite.so.2 comes out?
As for API changes, shouldn't there be some compatibility requirement on
APIs as libpcsclite.so evolves?
Valerie
On 04/24/13 04:05, Florian Weimer wrote:
On 03/01/2013 11:30 AM, Severin Gehwolf wrote:
Hi,
The bug for this review request is at:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=9000142
In PlatformPCSC.java unversioned native libraries are loaded by default
if no system property is specified. This could lead to a JVM crash if
the API of the native library changes, but the Java code still relies on
old API. The fix is to load versioned shared libraries instead.
Hmm. Why doesn't the "j2pcsc" library link against the right version
of libpcsclite.so?