sakura-it/kicad-myparts

Library of additional parts for KiCad for use with Sakura-IT projects

kicad-myparts's Issues

How to handle modification of libraries in existing KiCad projects.

Due to recent changes in kicad-myparts, a few of my older projects required modifications too. These changes to kicad-myparts were clearly good and welcome, but at the same time, they are generating additional work. We should think about some strategy, how to handle relations between components in this library and existing projects.

I thought about this for a while and came up with a few solutions:

• Include a copy of kicad-myparts in each project? Clearly not a good solution...
• Introduce branches in the kicad-myparts, switch branches depending on a project? Sounds unnecessary and complex.
• Explore how submodules are handled in git? The kicad-myparts repository could be included as submodule in every KiCad project we have in Sakura-IT organisation. To be honest, I don't know much about submodules in git yet, but it seems that they are able to reference a remote repository at a given point in time. Which would be perfect for situation where a project is generally finished and we don't want to break it (and at the same time, we'd be free to make further changes to kicad-myparts). See: https://git-scm.com/book/en/v2/Git-Tools-Submodules .

Any other ideas are welcome.