Re: How can I set permissions on shared source files?
Re: How can I set permissions on shared source files?
- Subject: Re: How can I set permissions on shared source files?
- From: "David \"Pita\" Kopp" <email@hidden>
- Date: Mon, 02 Aug 2004 13:17:12 -0600
Julian,
XCode has build in support for CVS as is, I believe. Subversion is
starting to get off the ground and become more useful, too.
Secondly, speaking from experience, using a VC system is very handy even
in single developer projects. It lets you track the changes you made,
and go back should one of them not pan out, something you just cannot do
without keeping many, many copies of your code checkpointed.
As for the permissions, it seems as though your applescript is probably
the best short-term solution. You may be able to add the script in as a
new build phase on your target, or in a new target. I would still press
for using a VC system of some sort in the long term... you will wonder
how you ever lived without it after using one for a while.
David
Julian Vrieslander wrote:
Thanks again to all who responded in this thread. I very much appreciate
the suggestions. Since everyone seems to be hot for VC systems, and since
Subversion seems to be the favored choice in that area right now, I went to
the web site and browsed the documentation.
I still feel that VC is not the best solution for the problem that I
described. Currently, I am the only person writing code on this project. As
the work progresses, there are two other people who periodically need to
pull files off my Mac, to test the program. One of them may be using a few
of my source files, but he will just be copying snippets into a MATLAB
program. The problem that I posed in my original post was a very limited
one: is there a simple or automatic way to set file permissions, so that my
coworkers do not have to change them before modifying their file copies?
They will not be adding those changes back into the project source code.
Subversion looks like it would be a very useful tool for the later stages of
our project, when there may be other people working on the code. Adopting
it right now would probably be a hassle. Note that I am only recently
coming back into programming, after a multi-year hiatus. I am a "recovering
physicist" and not a formally trained programmer. I grew up on FORTRAN,
Pascal, and Think C (that dates me, eh?). Right now, I am overwhelmed with
learning unix, Cocoa, OOP, Xcode, etc. I need to keep my programming
environment as simple as possible.
So for now, I will muddle through with my Applescript to change permissions,
and look at Subversion when I have a firmer foundation on the other stuff.
I think I read somewhere that Xcode 2.0 will provide built-in support for
Subversion, so perhaps my "conversion" will be easier after that.
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.