[Pkg-mono-devel] Packaging for 2.4
Cambell Prince
cambell at princes.co.nz
Tue Apr 28 04:20:45 UTC 2009
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. 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.
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.
- 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.
- What was the last upstream version that worked with the latest
packaging form svn?
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
For more info see:
http://palaso.org
http://projects.palaso.org
http://wesay.org
Regards,
Cambell
More information about the Pkg-mono-devel
mailing list