XCode doesn't respect Unix lock when opening subproject
XCode doesn't respect Unix lock when opening subproject
- Subject: XCode doesn't respect Unix lock when opening subproject
- From: Jim Wintermyre <email@hidden>
- Date: Fri, 1 Sep 2006 23:14:58 -0700
Is this one already a known issue?
It looks like XCode doesn't observe the Unix file permissions for the
project.pbxproj file when opening a *subproject* from within another
project in XCode. We have our project.pbxproj files checked into
CVS, and have watches turned on for these files. This means that the
project.pbxproj file gets gets its Unix permissions set to not
writeable when checked out. We do this so that the pbxproj file is
not "accidentally" modified every time a project is opened. We have
to explicitly unlock the file with cvs edit before making any changes
to the project.
This all works as expected when opening the project from the Finder.
However, if I open a project which contains another project as a
subproject, and open the subproject from the the first project inside
XCode, then XCode will actually modify the subproject's
project.pbxproj file, even though the file is set to not writeable!
This defeats the purpose of using cvs watches.
One interesting thing is that it seems that when a subproject is
opened this way, XCode does *eventually* notice that the file should
be locked, but by the time it figures it out (and updates the project
icon with the mini-lock icon etc.) it's usually too late as the file
has already been modified.
Jim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden