I have implemented a new implementation of the StartUpList and  
ShutDownList protocol. This is the type of sacred code that will be  
the most difficult to change and maintain between forks. I have always  
thought it could be simplified. My implementation is just an idea, to  
show the following concept.

This code is packaged, as three files containing all the knowledge  
needed to adopt it into your fork.

1. The implementation, (generated by  
PackagingCuis>>pkgSystemStartUpShutDown: 1)
2. The ChangeSet for integration into Cuis2.0
3. A ChangeSet for removal of the old cruft from Cuis2.0.

This should allow all forks to load file 1. without it effecting their  
code base, for testing and review. Then by inspecting the change list  
in file 2, they see how Cuis2.0 integrated it, picking the appropriate  
methods, and finally, they will need their own version of 3, until  
this protocol makes it into the mainstream of that fork.

File 3, is only applied once, File 2, you maintain your own local  
version, and File 1, you can then track the maintained version, in  
case there are any updates or fixes.

This is currently available in the "unstable" build of the  
InstallStream process for Cuis.

cheers

Keith
====
to get started - join https://launchpad.net/~rodents

mkdir trunk; cd trunk
bzr checkout --lightweight lp:~rodents/cuis/Cuis2.0vm.app
bzr checkout --lightweight lp:~rodents/cuis/base
bzr branch lp:~rodents/cuis/release
bzr branch lp:~rodents/cuis/stable
bzr branch lp:~rodents/cuis/unstable
./unstable/build.sh