Magus is our cluster for testing mports. It builds every port in a chrooted environment on multiple architectures and operating system version. It is currently in production. See the main magus page for more information.
This page serves as a todo list for the magus software package.
Client
- Move to parent/child model, will make many of these easy to fix. (Though need to figure out reloading then)
- fix db drop bug.
- let the user use a different mports
-j <foo>
- note when BROKEN is set as an info event.
- audit the chroot cleanup/setup. /tmp is a concern. /var/mail, /var/log, /var/db get spammed as well as /etc/passwd and /etc/group. passwd and group should be copied and restored between testing so we can verify account creation is working with scripts. Our current tarball already has several users like mysql. A fresh copy might make more sense. (src is available in the chroot)
- We need to figure out when to mark the chroot dead. In some cases, if files are written outside of /usr/local and /usr/X11R6, we should whack it. (acrobat8 and postgress 8.1)
- Some ports try to install to /home. Sometimes this is ok (postgres creates it's own user for use).
- Add some type of administrative checks between builds so the cluster and/or individual nodes can be halted without having to kill them. (cleaner)
Database
- keep pruning events schema
- Store LATEST_LINK during indexing.
Master
- make update script more configurable
Meta
- Docs!