On Sun, Oct 25, 2009 at 7:09 AM, Daniel Drake <d...@laptop.org> wrote: > Here's a patch that makes xs-activation server OS update information > based on what it has available in xs-rsync.
I like it -- thanks! It was in my TO DO notes with the earlier xs-activation work, and ended up cutting it. > I did this by creating > /etc/xs-activation-updates.cfg, a sample configuration file with > explanation is attached. This is code from oatslite which is deployed > in paraguay. Right... makes sense. I am a bit intrigued with the custom config file parser / writer (that is 3x the sloc of the whole xs-activation ;-) ). I am guessing the key motivator is that YAML, JSON and other config formats won't preserve ordering correctly, right? - is MyConfigParser used anywhere else? - odict is only needed on F9, correct? What is needed in terms of config parsing is pretty simple -- I suspect there are a couple of simple ways we could avoid depending on the ordering of the config file, with less code. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff _______________________________________________ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel