kicad-developers team mailing list archive

[Ouabache Designworks <z3qmtr45@xxxxxxxxx>]

I would not worry so much about a central repository. As your designs grow
you will find yourself using parts from a variety of different repositories
so the best way is to have an easy way to pull in outside parts and then
grabbing any repository is taken care of for you.

I would advise looking at IP-Xact IEEE-1685 for some of the lessons that
they have learned for dealing with large growing databases.

1) You must include the vendor name as part of your  descriptor. IP-Xact
uses a valid URL for the vendor name. That not only gives you a way to
manage the namespace but also shows you where to go if you need to update a
part.

2) You must be able to track a version number on any part. The golden
source for any part should be under revision control.

3) A flat list of libraries can get long and hard to use. You need to
support deeper depths

4) You do not want a library that only contains symbols and footprints. You
want the entire datasheet in one place. Once you select a part then you can
generate a library file for a schematic that only contains the symbols used
in that design. A component will be stored in a directory.


John Eaton