progress bar code in vb net 2010 10: Source-Code Management with Subversion in Objective-C

Making DataMatrix in Objective-C 10: Source-Code Management with Subversion

Listing 10 2. First steps to create a repository $ cd ~/Documents $ mkdir -p subversion_work/original_projects $ mkdir -p subversion_work/working_copy

Now, in the Finder, find the project folder for the project TemperatureConverter from 6 and copy it to the original_projects folder. You can do this from the command prompt if you are more comfortable working this way. Go back to the Terminal and type in the svnadmin create command to create your repository:

You won t see anything in response to this, so to confirm that you actually have a Subversion repository, type the verify command (all of the admin functions in Subversion use the svnadmin command followed by an argument use svnadmin help to get a list of these).

Notice that it says revision 0. That is because so far you haven t created any revisions (or even imported any content). By the way, you can do most of the things covered in this chapter by use of either the svn or svnadmin commands in the Terminal. We will be working in the Xcode Subversion Tools for the most part, but it is sometimes useful to work from the command line. NOTE: It is traditional when creating a Subversion repository to create three top-level folders, called branches, tags, and trunk, below the repository name. The trunk folder holds the main folder structure while the branches and tags folders hold information about branches in your revision history and tags that you can assign to specific folders within a revision to give them friendly, easy-to-identify names in addition to revision numbers. I have left these out in this chapter to keep things simple, and actually I rarely use them, but it is very straightforward to add these folders to your repository later on. Figure 10 4 shows what this repository looks like in the Finder.

This folder structure contains the configuration files for the repository and the database files that are used by the Subversion server to manage revisions. Now close this folder and never open it again! Seriously, it is a bad idea to make any changes directly to this folder, as it could corrupt the database that holds your precious code history. Leave it to Subversion.

You have the original files for your project and you have set up a Subversion repository. Now it is time to get the project under source-code management. Open Xcode if it is not already open. Close any projects that may be open. Find the SCM menu and choose the menu item Configure SCM Repositories... This will bring up the Xcode Preferences window at the SCM panel. Click on the Add button to create a new repository configuration: in the drop-down window give it a name like Local SVN repository. Make sure that the type of repository is set as Subversion; Xcode will also allow source-code management using other systems, such as Perforce and the older CVS, but these are much less common now than Subversion. You then need to add the Subversion settings. In the URL: box type in the location of the new repository in URI format; that is, file:///Users/ianpiper/Documents/subversion_work/svn. Hit the Tab key, and Xcode fills in the Scheme and Path boxes automatically (see Figure 10 5).

The other thing to note here is the green light below the list of boxes. As you complete each of the fields, Xcode tests the configuration to ensure that it can connect properly to the repository. That green light confirms that you have a connection since all you had to provide was the file location. When we look at hosted Subversion repositories shortly, you will see how it works when you have to authenticate. Now choose the Options tab and check the box that says Configure SCM automatically. This makes it easier to configure your projects when you add them to SCM. While you are on this window you might like to check out the Comparison Handling options. When you come to comparing revisions you can use the Xcode Tools or choose an editor such as BBEdit or Apple s own file-comparison utility FileMerge (you ll be looking at FileMerge more closely in 13). Unless you have a good reason to choose one of these other tools, I d advise sticking with Xcode for now. Choose OK to finish.