[Pkg-mono-devel] packaging libmono-saxonb8: interested / help

[Sebastian Dröge]

Am Montag, den 24.09.2007, 16:12 +0200 schrieb Stefano Zacchiroli:
> On Mon, Sep 24, 2007 at 01:13:48PM +0200, Sebastian Dröge wrote:
> > The best is probably to look at one of the existing packages and the CLI
> > policy[0]. For existing packages, maybe look at cecil or gtk-sharp2 :)
> 
> Thanks, for the pointers, I'll have a look at both ... and of course ask
> for a review before the actual upload. In case I'll end up with
> something working, can I ask to be added to your project on alioth just
> to be backed by a version control system? But before this read on ...

Shouldn't be a problem, it's Mirco Bauer <meebey at debian.org> who has the
required admin permissions for the alioth project :)

> On Mon, Sep 24, 2007 at 01:48:59PM +0200, Sebastian Dröge wrote:
> > >From looking at the saxon homepage I can't find any source tarballs,
> > only binaries. For packaging this you to use sources of course :) Maybe
> > I'm just too blind to find the correct link ;)
> 
> It's quite hidden indeed, my starting point is
> http://prdownloads.sourceforge.net/saxon/saxon-resources8-9.zip, but
> indeed it contains just a bunch of C# source code files. Is it possible
> that it is a kind of bridge between C# and the Java implementation?

It looks like these are meant to be built with ikvm, they're really just
"C# bindings" for the Java implementation. This will probably make
things more complicated, at least I know nothing about ikvm except what
it does :) And I fear that you might have the problems of both worls at
once...

> Besides (but even more if may guess above is true) the sources for both
> the Java and .NET stuff are tied together, maybe it wold be better to
> coordinate with the Debian java people for having a single source
> package and multiple binary packages?

When they're in the same source tarball that would make sense IMHO, if
they're in different tarballs better make it two source packages to not
have too large build dependency chains :)
But as the C# version of this looks like bindings to the java version,
either let the C# stuff build against the Java packages that are
currently there or ask the Java people to also build those C# bindings
in a binary package.