gEDA-dev: Errors found in drc2 backend no longer causes non-zero exit code

[Ales Hvezda]

> Poking at the extended gnetlist test-suite I've been working to add,
> I've found an unexpected change in behaviour between 1.2.0 and 1.3.0.
> 
> In 1.2.0, any DRC errors cause gnetlist to exit with code 1. (Usual is
> 0). In 1.3.0, gnetlist exists with code 0 in either case.

IMHO, gnetlist should always return a non-zero value for any failure 
or error.  I would qualify a drc failure as an error.  If something
should be ignored (not an error), then the specific drc test should
be disabled.

> Is it something we want to support? Should I just check in the golden
> files as 1.4.0 produces?

Maybe I missed something, but there are differences in golden file outputs
between 1.3.x and 1.4.0?  Which golden files are we talking about? Are 
the differences just cosmetic (display text)?

-Ales

PS. Ah, I just found the e-mail you sent me on the golden file changes.
I need to think about this.  Maybe we should catch up sometime on irc
and resolve this "in person". :)