Pierrick LE GALL <pierrick@koha-fr.org>
- isolated updates that can be executed only once - database self aware about its update level - notification in intranet screen that new updates are available
I think this is a good idea. Here are some more suggestions: 1. model the updates on sysV init scripts, so they can be started and stopped/applied and removed as needed by an upgrade; 2. the new updates notification should require deliberate action by the superlibrarian, else we may be violating user's privacy (also known as a "phone home" problem).
Update files will be Perl files in the update/updates dedicated directory, with numeric only filenames:
Can't they just start or end with a number, divided from the human-friendly name by a - or similar? It really is useful to have human-friendly names. Take a look at dpatch if you have a debian system nearby. http://alioth.debian.org/projects/dpatch/ - I'm sure there's been criticism of it, but I didn't locate it in a web search. Hope that helps, -- MJ Ray - personal email, see http://mjr.towers.org.uk/email.html Work: http://www.ttllp.co.uk/ irc.oftc.net/slef Jabber/SIP ask