However, what if libgeda stored a cryptographic signature/hash of
the symbol file contents along with the filename in the schematics?
The signature can be something along the lines of an md5sum string
(maybe
not so long, but long to uniquely identify the contents). When a
symbol
is loaded from disk, the signatures are compared and if they don't
match,
a warning is issued. Sorta like the existing symversion= mechanism,
but now it will not be possible for symbol changes to escape notice
from the designers. And should there be a valid symbol change, then
the
component is simply updated using Edit/Update Component.
Now back to the original problem: two symbols identically named
symbols will most likely not have identical signatures/hashes and it
would be impossible for the wrong symbol to be silently netlisted.
Comments on this idea?