Java dependencies - Was: Re: [Pkg-virtuoso-maintainers] Rebuildability of various binaries and shipped libraries for Debian packaging

[Olivier Berger]

Hi.

Le mardi 29 décembre 2009 à 13:19 +0100, Obey Arthur Liu a écrit :

> All JARs
> ========
> *.jar
> Virtuoso ships numerous pre-built java .jars built on source that is
> not included in the tarball. README.sesame2/3 and README.jena explain
> that the user has to get them manually. Because they are BSD-licensed,
> you are allowed to do this but this won't work for the Debian archive.
> Could you look into the possibility of using system installed versions
> of sesame, jena, slf4j... directly into the build system? Otherwise
> I'll have to patch one into the source code and I'll rather have you
> decide how you prefer to do it.
> Note that sesame and jena are not in Debian yet (but slf4j is, so you
> can try it with that) but I'm considering packaging them.

Regarding the Java libs/frameworks dependencies, I'd suggest to reserve
such work for a later time, i.e. concentrate first on the virtuoso
server and required client libs/odbc for KDE (and other apps), and try
to push that in the archive.

Then, the Java bindings may be reserved for a later time, eventually
adding the java packaging community in the loop.

At least this would provide a basis for testing installation of a
server, for other to contribute to different language bindings, and
additional tests.

Just my 2 cents,

P.S.: maybe I'm a little bit biased against Java packaging ? ;)

-- 
Olivier BERGER <olivier.berger at it-sudparis.eu>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)