I second this wishlist item wholeheartedly.
Note that the issue is not limited to Sun Java: IBM also ships an
"unlimited" crypto enabler separately.
I'm not keen on the auto-detection aspect of Steve Ihde's proposal #1,
since I happen to be keeping the JCE .zips in a separate directory. It
would seem better to at least allow the JCE file to be explicitly named
on the command line.
Other than this, I like proposal #1 better than #2 since it leads to
fewer packages and avoids having to divert the old files, which seems
ugly. The only situation in which #2 may be better is if one plans to
redistribute the generated .deb's to both eligible and non-eligible
countries. (More generally, if one is going to redistribute the
generated .deb's it would be nice if the package name could include an
indication of which JCE policy it was built with; but this can also be
done with approach #1.)
Another solution might be to treat the two files in question as
conffiles. Incidentally, there is a third file which one may want to
either turn into a conffile or replace at make-jpkg time (or maybe
both): jre/lib/security/cacerts.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
