Bug#408842: saxon 8.9: mono-side of the issue

[Stefano Zacchiroli]

On Mon, Sep 24, 2007 at 07:44:57PM +0200, Michael Koch wrote:
> As it is a different upstream source package anyway it makes sense that
> some csharp/.Net experienced packager handles this. Personally I have
> no clue about it.
> 
> Can you please handle that and speak with the mono team?

Yep, just did that.

In the end Saxon is basically a Java implementation. In addition to that
there is some glue C# code which provides just bindings from C# to the
Java implementation. The source package is one for the two types of code
together.

They mono guys suggested to start packaging the Java part per-se. Then
we can either have a separate source package with just the C# glue code
and having it dep/build-dep on the Java part or have single source
package which build both kind of packages. In both cases we should start
from the Java part. Then, if we chose to have a single source package, I
can ask the mono people to help me in patching it to build the C# stuff.

Cheers.

-- 
Stefano Zacchiroli -*- PhD in Computer Science ............... now what?
zack@{cs.unibo.it,debian.org,bononia.it} -%- http://www.bononia.it/zack/
(15:56:48)  Zack: e la demo dema ?    /\    All one has to do is hit the
(15:57:15)  Bac: no, la demo scema    \/    right keys at the right time