Re: Creating new Xcode projects into Subversion (Was: Xcode and Subversion)
Re: Creating new Xcode projects into Subversion (Was: Xcode and Subversion)
- Subject: Re: Creating new Xcode projects into Subversion (Was: Xcode and Subversion)
- From: John Velman <email@hidden>
- Date: Sat, 13 Jun 2009 17:08:40 -0700
- Mail-followup-to: John Velman <email@hidden>, email@hidden
On Fri, Jun 12, 2009 at 05:41:05PM -0700, Jack Repenning wrote:
> Incorporating Andrew's hints, and responding to questions asked after my
> last post, here's the New and Improved directions for creating a new
> project, within Xcode, so it ends up stored in Subversion:
>
> Before you begin, there needs to be a repository already set up, somewhere.
.....
> the SCM column shows; similar for the Detail tab area.
>
> You're in business!
>
> You can now remove ~/Desktop/NewProject, you don't need it any more.
>
>
>
> -==-
> Jack Repenning
> email@hidden
> Project Owner
> SCPlugin
> http://scplugin.tigris.org
> "Subversion for the rest of OS X"
>
I work alone, small projects on one computer. Following advice in
Anderson's "Xcode 3 Unleashed" I set up a local repository. I've been
using it, but basically have never (until just a minute ago) checked out my
project to a new folder. I simply commit everything after I've made some
changes and they seem to be working. (This must sound primative, but I
also do a lot of caveman debugging. I may be the original caveman -- my
first computer language was Fortran II, followed by the IBM Fortran
Assembly language that went with Fortran II). But I'm trying to learn
better practices.
Now to my question: What are good "strategy and tactics" for someone
working alone on one computer? I naturally looked up "SVN best practices"
on Google, and these make sense, but are sort of beyond what I would like
to know. Similarly, the "single user" advice I see is pretty much
mechanics, not tactics and strategy. I'd be happy if someone can point me
to something like a "single user subversion strategey and tactics" page.
In the meantime, here are a couple of questions:
Why is it a good idea to set up the project in a temporary place that will
be discarded?
If I set up as described by Jack Repenning (which sounds very good, and
I'll follow in the future), is it a good idea to keep the current working
version in the ~/src/Whatever directory, or discard this and check out a
new one every time I get back to working on the project?
Sorry if this is getting off-topic. If there is follow up I'll be happy to
take the continuation off-list.
Thanks,
John Velman
> _______________________________________________
> 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
_______________________________________________
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