IMPORTANT DATE : 04 Feb 2011
I have released an updated version which supports mono 2.10 (and previous versions) updated post version
UPDATE: I have released an updated version which uses new git repos here
This is a simple work in progress to make the process a bit easier. There are many good reasons not to follow various scripts on the internet that install mono over the top of your packaged distribution install. The fact the Mono 2.6 isn’t released yet is an overriding one because any application depending on mono might stop working, Banshee, Tomboy, F-Spot, etc
At the moment this scripts only supports Mono 2.6 branch + Ubuntu 9.10, see the TODOs! It will install mono into /opt/mono-2.6 and checkout & build in ~/mono-src/mono-2.6. Run it again to update your working copy and rebuild/install.
Please let me know if you like/hate/improve the script
Download script here http://patrick.qmtech.net/downloads/mono_parallel.sh
You will need these packages installed: build-essential automake libtool gettext mono-devel mono-1.0-devel subversion libpng-dev libtiff-dev libgif-dev libjpeg-dev libexif-dev autoconf automake bison flex libcairo2-dev libpango1.0-dev
If you’re looking for more than a DIY script my company QMTech offers commercial support for mono, please contact email@example.com / +44 (0) 161 660 2690 for details.
UPDATE (Thanks Ben): If you’re doing this on a server (no Firefox) you will also need to install: libxul-dev
UPDATE (7/FEB/10): Updated the package requirements
UPDATE (4/MAR/10): Updated the package requirements (added mono-1.0-devel, libcairo2-dev)
UPDATE (20/MAR/10): reworded to reference 2.6 branch not specific 2.6.1
Firstly a quick introduction since this is my first aggregator post, I’m Patrick McEvoy (firegrass). I’ve been using Castle for just over three years, and been working with mono and castle for around two years. It’s this mono/castle relationship that I will be mainly posting about.
Many of you might be wondering, where are we with Mono and Castle?
These days Mono and Castle work fine together, I use Castle and Mono web stacks in production environments. While there are some issues to be aware of they’re steadily getting ironed out and it’s nothing you can’t live with. Just ask on the Castle mailing lists.
What are we doing?
With the help of the Linux/Mono TeamCity agent, great efforts are being made to get all Castle tests passing on Mono. Failing tests range from simple mismatching line endings to real complex problems, so it’s gonna take some time.
Where are we going?
To increase Castle usage in the Linux world we need to package Castle for various Linux distros. I am only experienced in packaging for Debian/Ubuntu so I’ll only talk about that. Some of you may or may not know that all Debian packages are built from source and no binaries can be included in a source package. Therefore all dependencies must be packaged first before we can get anywhere near doing Castle. With the recent changes to release schedules and project separation this has been made a lot easier, as we can start with something easier like DP.
I am currently finishing off the debian Nant package upgrade to 0.86-beta, here’s a preview nant_0.86-beta1+dfsg_all.deb. This is needed as 0.85 won’t build Castle because it doesn’t have a mono-3.5 target.
If anyone wants to help just get in touch! That’s it for now!
Finally got round to getting my blog back online after Krzysztof was asking if I blogged for the Castle aggregator. I hope to posting a lot about using Castle project on mono, and the progress of packaging Castle for debian. As well as doing this work for commercial interest I also help run Clubhouse, which recently clocked over 300k page views with Castle/mono/mod_mono_apache.