-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I'm in favor of using the -java for JNI + supporting java classes.
FWIW, I support this also. But to go into more detail:
> - arch-dependant JNI libraries go into libocf-pcsc and similar,
> recommending (or depending on - I'll accept suggestions)
> libocf-pcsc-java (or similar).
In this case however I might argue for something clear in the arch-dependant
package name that it's a JNI library, eg., libocf-pcsc-jni instead of just
libocf-pcsc.
The main reason being that (I presume) the C library provides java-specific
functions and so there seems little reason to use it outside the context of
JNI.
So I guess my stance is then to either:
- - use a single package named libfoo-java with both the java classes and the C
library, or:
- - use two packages, these being libfoo-java containing the java classes and
libfoo-jni containing the C library.
I don't see any particular need to favour only one of these options as policy;
I can see circumstances where each option (splitting vs not splitting) has
its benefits.
Ben.
- --
Ben Burton
[EMAIL PROTECTED] | [EMAIL PROTECTED]
Public Key: finger [EMAIL PROTECTED]
A cigarette is the perfect type of a perfect pleasure. It is exquisite,
and it leaves one unsatisfied. What more can one want?
- Oscar Wilde
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9gKY+MQNuxza4YcERAieIAJ9tkfFPaRC3Bf5eXY3ixFhAIgvkFACgiFpi
YrMikfzP4kcqwilABtpxoIg=
=hjxN
-----END PGP SIGNATURE-----
