Excerpts from Christopher Warrington's message of Thu Dec 11 20:58:23 -0500 2008: > "William Morgan" <[email protected]> @ 2008-12-11 7:37 PM: > > > From what I remember there were some minor problems with the patch and > > we were promised a fixed version, and I think that's why it wasn't > > applied to the repo. But it may be sufficient for your purposes right > > now! > > Anyone remember what those were? I haven't been using Sup lately, so the > deficiencies haven't been bugging me. :-)
I do now, as it just bit me again: If you run a version of sup with the patch, it will crash on startup if any usual source lacks the :poll_interval property. If you have just installed the patch, this will bite you. If you have run a non-patched version of sup for any reason, it will blow away the :poll_interval properties on clean exit (because it doesn't recognize them, so it doesn't write them to sources.yaml) Suggest using default value when no value is supplied to solve the first case, probably emitting a warning to help slightly with the second case. I have no idea what to do about the second case more generally, except to perpetuate the patch to 'next' and 'master'. There may be other issues that I'm unaware of.
signature.asc
Description: PGP signature
_______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
