kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #27947
Re: [RFC] Future of GitHub libraries
-
To:
Jon Evans <jon@xxxxxxxxxxxxx>
-
From:
Clemens Koller <cko@xxxxxxxxx>
-
Date:
Sat, 18 Feb 2017 19:21:11 +0100
-
Cc:
KiCad Developers <kicad-developers@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<CA+qGbCAabYY9KW_WQWzSd=zEjkzBpTt+uu6TdxcA5_AvZZxGYw@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
Hello, Jon!
Thank you for your feedback, I fully agree with you. Just let me correct my own sentence:
> On Sat, Feb 18, 2017 at 8:31 AM, Clemens Koller <cko@xxxxxxxxx <mailto:cko@xxxxxxxxx>> wrote:
> Nobody should need to mess with an scm tool on a daily basis when doing electronics design.
> It should be wrapped nicely behind the frontends.
"Nobody should be forced to mess around with an scm tool..."
I am absolutely fine using git. BOMs, and some library generators (as well as the generated libs) are managed with git.
Unfortunately my commercial tool mixes the order of the objects in the ascii exports (schematics, layout as well as libraries) with each export in a way that scm tools fail.
I believe they do that intentionally to encourage (force) more people to use their "recommended" commercial tool to do the design documentation.
It's smells so fishy down that road and it's time to move over to something where I can hold the steering wheel in my own hands if I need to.
> (Of course, if you have already created Gerber files, there are ways to do it)
> https://github.com/madworm/KiCad-Stuff/tree/master/scripts/visual-diffs_on_gerber-files
> You can see in the README how this can be used directly from Git
You don't even need a script. You can just use Gerbv's "Fast, with XOR" rendering method you can select in the GUI.
Regards,
Clemens
On 2017-02-18 15:57, Jon Evans wrote:
> Hi Clemens, just wanted to give another perspective that goes against your last line -- Just wanted to say that some of us are very happy to use SCM daily.
>
> At my workplace, we use Git to store electronics designs and symbol/footprint libraries. It started with the electronics people who also do software (and so already knew how to use Git) and spread to the rest of the electronics people, who find it easy to use despite not being familiar with software version control. It works really well despite not being integrated into the tools we use.
>
> In my opinion, one important part of the data storage technology is to have a "diff" viewer for EDA data. Most of the commercial vendors provide something, although the quality and ease of use vary. But, if you can use a special tool to compare two revisions of a symbol, or footprint, or schematic, or PCB, then using Git as the underlying revision control mechanism works really well.
>
> This is why making a diff viewer for KiCad data is on my (long) list of "things that would take KiCad closer to the high-end commercial tools" that maybe one day I will have a chance to work on -- I have seen some people talking about this feature request on forums, but as far as I can tell, no one has made a proof of concept yet.
>
> (Of course, if you have already created Gerber files, there are ways to do it)
> https://github.com/madworm/KiCad-Stuff/tree/master/scripts/visual-diffs_on_gerber-files
> You can see in the README how this can be used directly from Git
>
> Best,
> Jon
>
> On Sat, Feb 18, 2017 at 8:31 AM, Clemens Koller <cko@xxxxxxxxx <mailto:cko@xxxxxxxxx>> wrote:
>
> Hi, Andy!
>
> On 2017-02-17 19:51, Andy Peters wrote:
> >> On Feb 17, 2017, at 8:31 AM, Clemens Koller <cko@xxxxxxxxx <mailto:cko@xxxxxxxxx>> wrote:
> >> And: In the long-term we might also think about using git for project and design management and versioning. (We could even store undo's and redo's in git?)
> >
> > Except that not everyone likes or uses git. I use Subversion for my projects.
>
> Sure. That's why people created git svn...
> Sometimes it just might be sufficient to consider that there are already some solutions out there.
>
> But as others suggested already:
> Nobody should need to mess with an scm tool on a daily basis when doing electronics design.
> It should be wrapped nicely behind the frontends.
>
> Regards,
>
> Clemens
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> More help : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
>
>
References