Does the library editor tool lock a file while editing it?

Question

I am working in a git controlled evnvironment with several other engineers. Currently we each have a local copy of our libraries that are sync'd through git. The problem of merging libraries files after a Git pull is becoming excessive.

We'd like to store all files in a folder on an NFS server accessable by all users. The libraries would still be version controlled by git, with a periodic commits. When an engineer is editing a library, the file is read only to all other users. the other users can view but not concurrently edit the file.

does the eagle library editor tool lock open files?

If not, is it possible to easily integrate this feature? without any other version controll or check-out software.

autodeskguest · Answer

Jesse Banks wrote on Tue, 13 May 2014 15:05

I am working in a git controlled evnvironment with several other
engineers. Currently we each have a local copy of our libraries that
are
sync'd through git. The problem of merging libraries files after a Git
pull is becoming excessive.

We'd like to store all files in a folder on an NFS server accessable
by
all users. The libraries would still be version controlled by git,
with
a periodic commits. When an engineer is editing a library, the file is
read only to all other users. the other users can view but not
concurrently edit the file.

does the eagle library editor tool lock open files?

If not, is it possible to easily integrate this feature? without any
other version control or check-out software.

Hello Jesse,

Don't worry about all the haters, you're doing the right thing using

serious revision control for your libraries. I have worked at a lot of

companies and library mismanagement is the number one reason boards come

back not working. I have over 1500 unique devices in my library and it's

been in SVN control since the beginning (over a decade now).

I would however recommend that you don't use an NFS mount but force

everyone to use revision control client to check out latest version to

their machine. I think that is cleaner and you can then update your local

copy of the library at a time suitable for your project (which might not be

suitable for another).

The short answer is don't expect EAGLE to change it's behaviour. And I'm

not sure I want it to.

Use your revision control client to get the effect you would like. I

haven't used git but if SVN clients can be configured to auto-lock certain

files then certainly git should be able to do it. If I lock the file using

SVN then no one else can get a lock on it. And the file is read-only on

the file system until SVN gets a lock. I think that is the effect you are

after.

That would be my advise. Another reason for wanting a full update report

so you can see what has changed in the library under your feet -- that

would help you out greatly in your situation (see thread from a few days

ago on that topic).

Cheers,

James.

--

James Morrison ~~~ Stratford Digital

Specializing in CadSoft EAGLE

Online Sales to North America
Electronic Design Services

Take advantage of v7 License Promotion right now at

http://www.eaglecentral.ca

--

Web access to CadSoft support forums at www.eaglecentral.ca. Where the CadSoft EAGLE community meets.

AnalogNotes · Answer

Jesse Banks wrote: 
 I exist in a Git + NFS environment and need to find a solution in this space. The rev control problem is the origional problem: merging XML files. Our current tools are not capable of identifing file changes correctly, and it takes a ton of man hours to resolve. 
 
 if two users have added parts to the same library (think resistors, caps, inductors) the merge tool sees the new entries in contension. each user has appended the xml list in the library and the merge tool thinks they are in conflict, instead of seperate new entries. maybe a merge tool change is in order. 
 It's too bad that Cadsoft switched to the XML file format. Sigh. Oh well, we're here now. I started to write some XML tools to work with EAGLE files, but then I gave up and just started using a couple export ULPs to create script files that are easier to deal with under revision control. At some point, I'll go back and see what I can do with the XML... 
 We could probably just keep file revision control using git if the xml merge tool were more powerful. Any sugestions? 
 Check out: Project: Merge - Professional Two/Three-Way XML Compare and Merge The "3DM" XML 3-way Merging and Differencing Tool https://versioncomparer.codeplex.com/ There are some academic papers online about different diff and merge algorithms for XML, if you're having trouble sleeping. Another option might be to invest in one of the dedicated library management tools that can export EAGLE libraries...