well, if i do that, ill probably use a distribution i'm used to, like archlinux, it would also give me greater chances of being able to build and/or maintain a spring-headless package without pulling dependencies like X, sdl, gl, alsa and similar (i'm not entirely sure if it is viable with the current spring headless though?)hoijui wrote:a VirtualBox image for a botrunner .. i would like that. a problem i see there though, is how to maintain it painlessly. redistributing a 1GB image each time a new spring version comes out is not a nice thing of course. same with new AI versions.
but regardless of the distribution, would it be really that hard to update a package? although i would advise against it, it might be possible to include in the botrunner a part that executes system updates (or at least those limited to spring and their dependencies). since here we have the assumption that all botrunners are the same when it comes to configuration, it might even be possible to include some sort of custom code executions given from springgrid. and that should only be included for the virtualbox image botrunners, even then it might make people uneasy
as far as AI versions are concerned, they can easily be shared in binaries if we're using the same image - which implies the same architecture. hugh has also included an attempt for botrunners to download maps/mods/ais (some or all three), it would copy the AIs in spring source directory and try to compile it, although i'm not sure how that went