No subject

argument for splitting out the Web bits as a separate package as well;
for a multi-server install, you probably won't want to install the Web
on each server.

Are you aiming at getting the packages accepted into the official
distro repositories? It would be great to document this understanding
for the future (particularly if there are clear TODOs to get to the
point of having the packages accepted by the distros). Also, let us
know if there are things that we can do that would reduce the work
required to build packages.

> As promised I've been working on creating an evergreen livecd. I'm
> mostly done with getting a basic evergreen install working in the
> livecd environment, but need to do some testing on a physical machine.
> (Since the livecd works by loading a lot of things into RAM, it is
> hard to work with in a virtual machine, with my spec anyway.) In the
> next few days I should have an example iso to demonstrate. However due
> to the size of this (currently 936MB) I I'm not sure I have space to
> host it myself. Would it be possible to use one of the Evegreen
> community's servers for hosting this?

Wow, awesome!

I'm sure that server space can be arranged - we can poke the server
admins on #evergreen to lobby for an account for you on one of the
machines.

> I've also started looking at boxgrinder[1], a fedora based tool for
> building virtual machine images. Once I have this building working
> Evergreen installs, I plan to look into using it as the basis for
> thorough clean install tests. Whilst there is already exists an
> evergreen testing server based on buildbot, this performs unit tests
> on the codebase after it has just been built. Since boxgrinder allows
> the dynamic generation of custom virtual machines, tests could also be
> automatically performed on a functioning clean installation.

Sounds good!