We can probably set up a Jenkins build - if you can assign us some place to put it. So Jenkins would automatically do a build every release. The pace of change is such that I don't particularly want old versions of MAUS kicking around without some good reason.

We already build occasionally on the RAL PPD machines for testing, so probably not much needed on PPD side, just some disk space.

We mainly just need an account (I'm worried about what happens when I leave and all my accounts expire, thus breaking stuff). And enough diskspace to install it.

Standard for collider experiments maybe... I've never heard of a neutrino experiment (ie. comparable to our size) who successfully had RPMs.

I would love RPMs but it sounds like a few weeks worth of fiddling after a week to get the RPM in the first place.

(Or rather since I'm citing examples: SNO, SNO+, Braidwood, and MiniClean I know don't. And I would be surprised if ATLAS had RPMs because they have an incredibly complicated system for setup and I don't remember seeing another way of doing things)

Grr redmine just lost my comment.

Source rpm might not be too bad. Not talking about splitting the build scripts, rather put everything in one rpm I think and distribute only source code (rpm system then runs build script)...

I was mistaken as now the LHC experiments have moved on to using CernVm to distribute and install their software. As for neutrino experiments. Well ISIS along with other partners have developed a very nice analysis framework, 'Mantid', that is distributed as rpms. If you hadn't invested so much time in MAUS already then i would have thought that Mantid may have been a good solution. It is got 16 people working on it full time and has been around for 5 years now, it has a plugin architecture so you can easily extend it using python.
Anyway that is all beside the point.
What do you get out of Jenkins? I assume you are building a number of C/C++ libraries specific to the platform plus a python package. If this is the case then it is relatively easy to knock up an rpm. If you have dependencies on other packages that are not in rpm form then you can package their libaries as well, depending on licences. Having built the code it installation of MAUS hard?
I will try and have a word with Rob tomorrow and see what other options are acceptable.

Installation done and available on /opt/ppd/mice/software/maus . Wiki has been updated with instructions.