On Fri, 2004-11-19 at 12:58 +0100, Arnaud Vandyck wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Fri, 19 Nov 2004 17:26:02 +0800,
> Cai Qian <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> > I am packaging a Java package now. I found in upstream source there are
> > some pre-supply .jar and .so files (because he works under windows).
> > Most of them exist in some Debian java libraries, so I can relink it.
>
> Yes.
>
> > However I don't know which packages contain Base64.jar and zeus.jar.
> > Does somebody know?
>
> Don't know. There already is a base64 (de)coder in libcommons-codec-java
> - From the Jakarta project.
>
> > If they don't, should I ask upstream author to supply these files source
> > code and include them?
>
> Yes, and make two separate packages.
>
These 3 jar are not exist in Debian.
-rw-r--r-- 1 caiqian caiqian 1417 2004-04-11 22:12 Base64.jar
-rw-r--r-- 1 caiqian caiqian 82872 2004-07-12 23:55 shutter.jar
-rw-r--r-- 1 caiqian caiqian 96607 2004-04-26 13:57 zeus.jar
You mean I have to make 3 separate packages as form libxxx-java, and
then install them into /usr/share/java?
I found that Java Policy said "All jar files must have a well-documented
CLASSPATH". What does that mean? I seems I never use CLASSPATH until a
wrapper in /usr/bin call the following.
/usr/bin/java -Djava.library.path=/usr/lib \
-classpath /usr/share/java/shutter.jar: ...
> > Another question is these .jar and .so files are up to 3M, Is it right
> > to delete them in original tarball before upload?
>
> Yes, good idea.
>
> Many thanks for your participation in Debian-Java,
Don't mention it. Thanks for help.
>
> Cheers,
>
> - --
> .''`.
> : :' :rnaud
> `. `'
> `-
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
>
> iD8DBQFBnd/q4vzFZu62tMIRAmOvAKC6ZpT1DskwZx/YMoeORfCH3y+/kgCgt438
> T+rYhitEfMMxa1BYM+h7QO8=
> =7mMp
> -----END PGP SIGNATURE-----
>
--
Cai Qian
