Mono 2.0.1 package (triggers major packaging transition, please read in full)

Binary package hint: mono

Attached is a source package for Mono 2.0.1. This is a 0ubuntu1 package - not because the work has been done by Ubuntu developers (it hasn't), but because the Debian pkg-mono team would like to get as many talented packagers helping us with a major packaging transition as possible - and that's hard to do when we need to wait around for Debian NEW.

The background to this transition can be found at http://wiki.debian.org/Teams/DebianMonoGroup/Mono20Transition, and the short answer to "why bother" is "it shrinks the install size for Mono apps by up to 40%"

This transition is split into three sections, which must be completed (and I mean 100% completed, certainly for steps 2 and 3) in order:
1) Move the core Mono stack from 1.9.1 to 2.0, including the changes introduced to Debian packaging in 2.0
2) Transition all *APPLICATIONS* which build-depend on Mono to compile against a different compiler (see http://wiki.debian.org/Teams/DebianMonoGroup/Mono20Transition#head-67c13a005dab7f510b0fd1ee8db7a30689e89669 or ubuntu-devel@/ubuntu-motu@ for more detail)
3) Transition all *LIBRARIES* which build-depend on Mono to compile against a different compiler (see point 2 above).

Completing the steps in order is vital to a smooth transition, as the build-deps required by packages has changed. Once step 1 begins, applications with build dependencies on Mono are highly likely to fail (until they are altered to take account of the transition). Applications with a RUNTIME dependency should still run and install smoothly.

This source package, along with eight others (which will be receiving bugs like this shortly) contain the "core Mono stack". I'll be trying to coordinate this stuff personally with a series of 0ubuntu1 packages, and syncs from Debian Experimental. One package already slipped in, as due to assorted reasons it's in Unstable (http://packages.ubuntu.com/jaunty/mono-vbnc) so the number of packages to migrate is already smaller than when you started reading this.

A more detailed explanation of how to help will be posted to the mailing lists, to help app & lib developers through the transition (and hopefully accelerate the transition for Debian as well)