@Anonymous wrote:
Hello,
We have multiple users using Eagle on the same project, but the issue continually comes up when it comes to versioning and keeping current while others are working. We'd like to see some type of check in - check in / out of projects to alleviate this problem. Is something like this possible with the current software? If not, we'd like to make a feature request for it.
Derrick Hopkins
Ratpac Dimmers
Hi Derrick,
EAGLE is an XML file format so you can use standard version control systems with it, and I would recommend people do this anyway as it will save their bacon at some point! I use GIT for all my projects. However, you should bear in mind that any VCS can only cope with so much difference before you end up with conflicts so two people working on one design and merging changes is going to end up getting difficult very quickly.
I haven't verified because I tend to work on my projects myself, but I think if you are disciplined this might work. I think the best way for it to be done would be to have one person in charge of the master design and others work on separate parts of a design in their own .sch/.brd and then when they are ready, they commit the change to the VCS and the person in charge of the master can import these into the main design. This can be simplified somewhat by using the design block feature of v8 for the various parts of the design other people are working on and then the .dbl design block can be imported via that mechanism.
You'd need to remember that design blocks can't be "updated" in place with newer versions. Changes to the base design block will require it to be deleted from the master and re-imported to get it updated. I'd like to see improvements in this area.
Best Regards,
Rachael
