[Pkg-mono-devel] Packaging for 2.4

[Mirco Bauer]

Hi Cambell,

On Tue, 28 Apr 2009 11:20:45 +0700
Cambell Prince <cambell at princes.co.nz> wrote:

> Hi,
> 
> Currently we've got a repository for mono2.0 on ubuntu (hardy,
> intrepid, jaunty) at http://packages.palaso.org.  We skipped 2.2, but
> now we're upgrading to 2.4.

As as we did, 2.2 was too buggy for our needs.

> I've checked out the latest svn of the
> packaging, and I'm using the mono 2.4 tarball.  Currently we maintain
> our own repository because we want to include a number of our own
> patches that didn't make it in to upstream 2.0, and now we have a few
> patches that didn't make it in to 2.4 that we want included.

If the patches you include are important enough such as resource leaks
or crashes, feel free to submit them via the debian BTS and I will
apply them too! I regularly pick and backport patches from
upstream's SVN when they look important enough.

> 
> Here are a few questions:
> 
> - Splitting the build into arch and arch-indep with
> --disable-mcs-build doesn't seem to work because of the dependency on
> mcs (mscorlib) in the building of the mono docs.  A convert.exe is
> built to process the docs.

For me this works, as part of the DFSG I had to remove the binary that
convert.exe uses (HtmlSomethingPack) and with that disabled that part.

> 
> - I understand that the cil assemblies can be packaged as
> architecture independent, but what is the motivation for having
> separate build targets?  The separation could be managed when the
> install targets are processed.

Well, for X86 and AMD64 this doesn't seem to be an issue, but ever
thought of all the other architectures we support? Such as arm, powerpc
and s390, they need about 20 hours wasting their cycles to build
useless bits that are not included in the final packages. We made this
thing working because there was an important need not because someone
was bored or something :)

> 
> - What was the last upstream version that worked with the latest 
> packaging form svn?

Not sure what you mean here, last upstream version? The stuff in SVN
(now in GIT btw) was against mono 2.0.1, and 2.4 packages are in work.

> 
> As this is my first post to the list so here's a brief introduction:
> 
> I work at Payap University, Thailand as part of the University's 
> Linguistics Institute.  Our software group is called 'palaso' and we 
> develop software that is used in minority language communities.  For
> the last 12 months we've been contributing to the mono project in
> various forms, and maintaining mono 2.0 packages for ubuntu on our
> repository http://packages.palaso.org

Thanks for getting in contact with us, feel free to join the
#debian-mono IRC channel on OFTC. Thats where we hang around and
coordinate collaborative packaging.

> 
> For more info see:
>     http://palaso.org
>     http://projects.palaso.org
>     http://wesay.org
> 
> Regards,
> Cambell
> 
>

-- 
Regards,

Mirco 'meebey' Bauer

PGP-Key ID: 0xEEF946C8

FOSS Developer    meebey at meebey.net  http://www.meebey.net/
PEAR Developer    meebey at php.net     http://pear.php.net/
Debian Developer  meebey at debian.org  http://www.debian.org/