Theo Van Dinter wrote:
they're just config files, but the rules are a pretty big component of
the product. In any case, there has only been 2 commits (one of which
was the addition of a "1;") in the last 6+ months from all 5 committers
combined, so it's definitely not a pressing issue.
Um. Where were you looking? I haven't been doing a ton of updates, but it's
more than 2 in 6 months.
I was referring to committers that aren't PMC members.
Anyway, the 3.1.6 queue is empty now, except for bug 5044. I just want
to make sure that you weren't reserving exit code 2 for anything before
I commit the sa-update lint changes.
Geez, you guys cleared it out without me. <sniff>
I think 2 is probably fine, though the description is incorrect (or misleading
anyway):
+An exit code of C<2> means that a lint check of the current site config failed.
It means that linting of a channel failed. It could have been the site
config, or it could have been the channel. There's no way to differentiate.
No, that's correct. It first lints just the local site config (and
exits with 2 if it fails). Then it does the channel updates, as before,
exiting with 4+ for whatever reason (lint failure, bad checksum, etc).
I've got it linting the site config by itself first so that we don't
waste mirror resources on installs that are never going to successfully
lint a channel update due to a broken local site config.
Daryl
