1 |
Ciaran McCreesh wrote: |
2 |
> On Thu, 2 Mar 2006 11:35:12 +0100 Paul de Vrieze <pauldv@g.o> |
3 |
> wrote: |
4 |
> | * Just because breaking policy breaks a QA tool, but is guaranteed to |
5 |
> | never break itself (formatting policy, like space vs. tab etc.) |
6 |
> | does not increase the severity of the breakage. |
7 |
> |
8 |
> I'd argue against this one. See, it's possible to deliberately |
9 |
> circumvent some of repoman's checks by doing weird whitespace and syntax |
10 |
> trickery. There's also no way to fix repoman short of writing a fully |
11 |
> functional bash parsing tool -- which is complicated enough that even |
12 |
> bash doesn't have one that works in some releases... |
13 |
|
14 |
QA shouldn't have to depend on the tools you use. The final say should |
15 |
be the human interaction. If doing weird white spaces breaks the tool, |
16 |
but really isn't a QA issue outside of neatness, it shouldn't be waving |
17 |
red flags. Yes, its probably something that should be fixed, but it |
18 |
shouldn't be a critical one just because the tool is broken and can't |
19 |
handle the weirdness. |
20 |
|
21 |
-- |
22 |
Lance Albertson <ramereth@g.o> |
23 |
Gentoo Infrastructure | Operations Manager |
24 |
|
25 |
--- |
26 |
GPG Public Key: <http://www.ramereth.net/lance.asc> |
27 |
Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742 |
28 |
|
29 |
ramereth/irc.freenode.net |