Re: gEDA: One more tester!

["Darin Ingimarson" <darin-at-NOSPAMk2t_dot_com>]

Thomas,

Thanks for the great suggestions (esp about component verification).

What I would like to see eventually is something similar to the way
that you can configure CVS to for checkins. You can set it up to run a 
script when someone checks in a hunk of code to ensure that all 
new modules adhere to coding standards, compile correctly, etc.

But first, I need to get the basics down! I'll leave the fancy stuff until
later on.

    -darin

>To get the most out of the database it should be posible for any
>end user to submit new components to it. But to keep a high level
>of quality of the database, there should be some kind of verification
>process of each component. Some things like pin spacing, pad sizes or 
>minimal set of attributes could be checked by the editing tool. But
>there are other things which should be checked by a human. In general
>there is no problem, but since this check can take some days, but the
>end user needs his component right now, he almost certenly is going to
>use his new, non-verified component in his design. In the case he
>did a good job and his component meets all design ruls there is no 
>problem. The component will get released and his design is consistend
>with the library (a update of his design might be neccesary, to change
>the refereces from the local to the global library). BUT, if he did a
>poor job or he uses for some reason special design ruls, it will result
>in a inconsistensy. While this should be alowed in some special cases
>(resulting in the need of a local library!) it should not be alowed in 
>general!