[Pkg-mono-devel] Packaging IKVM: inclusion of 3rd-party sources
David Paleino
d.paleino at gmail.com
Thu Dec 4 10:35:57 UTC 2008
Hello,
as part of the Debian Mono Team, I'm trying to get ikvm [1] into an usable
state.
I've contacted the upstream author, since the build process is *nasty*, at
least: it *requires* GNU Classpath's and OpenJDK's sources (upstream specified
that a *full* *build* of OpenJDK is required, because of some generated files),
and including them inside debian/ is not a great idea to me because:
1) *enormous* diff.gz;
2) security headaches -- code duplication is never nice;
3) hard maintainability.
Upstream noted that he does provide pre-generated .zips with all the needed
files to build IKVM. I suppose that this makes ikvm non-free (pre-built
binaries), but the binaries are effectively coming from software in main (GNU
Classpath and OpenJDK).
How should I behave here?
1) Should I include the sources in debian/ and do all the needed steps to get
a full compile? (notice that if we follow this, each IKVM build will include
an OpenJDK build...)
2) Or should I make two separate (source) packages, "ikvm" and
"ikvm-build-deps", with the former Build-Depends on the latter? Also, would
this be acceptable? (probably ikvm-build-deps would go into non-free, and
ikvm into contrib?)
Any suggestion is very welcome.
Regards,
David Paleino
[1] that is, the JVM ported on Mono
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-mono-devel/attachments/20081204/5c7c50ba/attachment.pgp
More information about the Pkg-mono-devel
mailing list