On Fri, Jun 30, 2006 at 07:25:05PM +0100, Justin Mason wrote: > >I'm also concerned that our whole sa-update system is a bit immature to > >trust it to distribute automatic code updates. Down the road I think > >it's a great idea (it works for the anti-virus folks, and it should > >work nicely for us too,) but I'd rather get more people using sa-update, > >get more work done on sa-update, etc. > > Either way, it's quite easy to switch from one to the other; since the > build/mkrules script will turn "loadplugin" into "tryplugin", since a > failure to load the latter is not an error, and since the sa-update script > can simply remove rules/*.pm when building the tarball, it's a matter of a > 1-line change in the "build/mkupdates/run_part2" script.
Aha. Well, case in point. The automated system to generate updates, which uses mkrules, will only work for the latest development version. Whenever we branch off 3.2 and start work on 3.3, the system will stop functioning for 3.2. This is why 3.1 updates are done manually whenever someone (me usually) gets around to doing it. -- Randomly Generated Tagline: "An open mind has but one disadvantage: it collects dirt." -- a saying at RPI
pgp45lHstnB1Y.pgp
Description: PGP signature
