• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: what versioning system do you recommend?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: what versioning system do you recommend?


  • Subject: Re: what versioning system do you recommend?
  • From: Oftenwrong Soong <email@hidden>
  • Date: Mon, 18 Jan 2010 22:04:28 -0800 (PST)

On Mon, January 18, 2010 8:32:54 PM, Jim Thomason <email@hidden> wrote:
>> What do you recommend me using?
>
> If you really want a starting point, look at Subversion. It's easy,
> powerful, and plays nice with XCode. But pick one you like above all
> else.
>
> -Jim....


I use Subversion and haven't looked back. I, too, use the command line interface. It's a friendly program and easy to use. If you try it, here are some notes from my experience:

1. The svn-book is well written and contains the theory of operation and all the proper incantations. It is here:

http://svnbook.red-bean.com/

2. The svn pre-installed (version 1.4.4) is an antique. I run 1.6.6. Supposedly there are prebuilt binaries here:

http://subversion.tigris.org/getting.html

or there is Fink or MacPorts but I prefer to build it myself by downloading the source tarball and issuing the three-command salute:
      ./configure
      make
      sudo make install

The most important thing is to extract the sources into a folder whose full path does NOT contain ANY spaces or weird characters that might trip up a shell script (the folder itself or any of its parent folders). Otherwise ./configure gets confused and make produces all sorts of garbage. With a custom build, the binaries should go in /usr/local/bin. Apple's version should remain in /usr/bin. $PATH has to be set up so bash sees the custom version first. That can be done by putting the following into ~/.bash_login or one of those files: export PATH="/usr/local/bin:/usr/local/sbin:$PATH" (Of course, it's a good idea to issue "which svn" to make sure you're running what you think you're running.)

3. If you build the newest svn, I wouldn't use it from within Xcode. Who knows which version Xcode will run, and if it runs the new version, who knows what changes in the command line interface or back-end libraries might break things... I prefer to play it safe and just use the command line.

Hope this is helpful...
Soong




 _______________________________________________
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

  • Follow-Ups:
    • Re: what versioning system do you recommend?
      • From: Joar Wingfors <email@hidden>
References: 
 >what versioning system do you recommend? (From: Martin Beroiz <email@hidden>)
 >Re: what versioning system do you recommend? (From: Jim Thomason <email@hidden>)

  • Prev by Date: Re: what versioning system do you recommend?
  • Next by Date: Re: what versioning system do you recommend?
  • Previous by thread: Re: what versioning system do you recommend?
  • Next by thread: Re: what versioning system do you recommend?
  • Index(es):
    • Date
    • Thread