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

Jesse Banks wrote:

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.

If you're having a problem merging libraries, that suggests to me that your libraries are too large and/or too complex.  Have you considered splitting them up and using more small library files?  Are you really making that many changes to your libraries?  If so, merging issues are probably a symptom of a larger work flow problem.  The whole point of a distributed revision control system like Git is to keep local copies of everything and work independently, then periodically merge changes.

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.

Speaking as a Linux System Administrator, NFS is evil!  If you don't have to, don't use it.  I'd suggest Unison instead: Unison File Synchronizer

If you really want to have a central master repository with file locking, you will probably be better off switching to Subversion (SVN) instead of using Git.  Here's a discussion of file locking with SVN: http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.advanced.locking  That seems like a better fit for what you are talking about...

Jesse Banks wrote:

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.

If you're having a problem merging libraries, that suggests to me that your libraries are too large and/or too complex.  Have you considered splitting them up and using more small library files?  Are you really making that many changes to your libraries?  If so, merging issues are probably a symptom of a larger work flow problem.  The whole point of a distributed revision control system like Git is to keep local copies of everything and work independently, then periodically merge changes.

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.

Speaking as a Linux System Administrator, NFS is evil!  If you don't have to, don't use it.  I'd suggest Unison instead: Unison File Synchronizer

If you really want to have a central master repository with file locking, you will probably be better off switching to Subversion (SVN) instead of using Git.  Here's a discussion of file locking with SVN: http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.advanced.locking  That seems like a better fit for what you are talking about...