None at all. I use subversion on both my Arduino directory and my eagle directory. With a large project, or with multiple people, I would likely put one project with both hardware and software branches into one or two repositories, but just maintaining control of the Arduino and eagle directories works for my personal stuff (where I'm mostly concerned with having my various machines at work and at home synced up, less so with the revision history).
could you elaborate on svn with eagle usage?
My guess is, when you do an update, schematics and board layouts will be replaced as a whole, as they are binary files. Wouldn't the files get chopped otherwiese?
Shure there is file splitting e.g. as eagle libs, but as I understand eighthave, there is no way to split up a certain schematic or board layout in hierarchically consistent files. Thus, every sheet
in an eagle schematic could represent an own file etc. This would be required for really collaborative work on an open hardware project.
Does anybode know how the internals of the open source schematic & layout projects gEDA/PCB (http://www.geda.seul.org/
) would allow file versioning?
Well, BTW, there is now http://www.fritzing.org
, als mellis annouced on the arduino blog: http://www.arduino.cc/blog/?p=11
They hopefully consider a collaboration feature...