Setting up a local SVN repository

 You can create a Subversion repository on your computer and use file:// scheme to interact with it locally. This approach can help you use Subversion locally to track personal files and single-person projects.

The following procedure creates a minimal environment for an existing project. It converts a directory with a project into a working copy of a newly-created local Subversion repository. As result you can modify the files in the working copy and track the changes in your local repository.

On Unix:

  1. Create a parent directory .svnrepos where you will place your SVN repositories: $ mkdir -p $HOME/.svnrepos/
  2. Create a new repository MyRepo under .svnrepos: $ svnadmin create ~/.svnrepos/MyRepo
  3. Create a recommended project layout in the new repository: $ svn mkdir -m "Create directory structure." \  file://$HOME/.svnrepos/MyRepo/trunk \  file://$HOME/.svnrepos/MyRepo/branches \  file://$HOME/.svnrepos/MyRepo/tags
  4. Change directory to ./MyProject where your unversioned project is located: $ cd $HOME/MyProject
  5. Convert the current directory into a working copy of the trunk/ in the repository: $ svn checkout file://$HOME/.svnrepos/MyRepo/trunk ./
  6. Schedule your project's files to be added to the repository: $ svn add --force ./
  7. Commit the project's files: $ svn commit -m "Initial import."
  8. Update your working copy: $ svn update

Comments

Post a Comment

Popular posts from this blog

How Things Used To Be

Hi friends, I don't know who wrote this article and some of it may not be accurate but it is still interesting musing... Rhio Next time you are washing your hands and complain because the water temperature isn't just how you like it, think about how things used to be. Here are some facts about the 1500s: Most people got married in June because they took their yearly bath in May and still smelled pretty good by June. However, they were starting to smell, so brides carried a bouquet of flowers to hide the body odor.
Read more

Controversial programming opinions

One of the very first ideas we had for this blog was to convert some of the wonderful gems of the early era of our site, the undisciplined period, to blog posts. Questions that were once enthusiastically received by the community, but no longer fit Programmer’s scope. The first deleted question I’ve chosen is Jon Skeet’s “What’s your most controversial programming opinion?” question (available only to 10K+ users, sorry), a +391 scored question that was originally asked on Stack Overflow on January 2, 2009. What follows are twenty of the highest voted answers, in random order…
Read more

Some lesser-known truths about programming

My experience as a programmer and as webmaster of Mises.org has taught me a few things about writing software. Here are some things that people might find surprising about writing code: A programmer spends about 10-20% of his time writing code, and most programmers write about 10-12 lines of code per day that goes into the final product, regardless of their skill level. Good programmers spend much of the other 90% thinking, researching, and experimenting to find the best design. Bad programmers spend much of that 90% debugging code by randomly making changes and seeing if they work. “A great lathe operator commands several times the wage of an average lathe operator, but a great writer of software code is worth 10,000 times the price of an average software writer.” –Bill Gates A good programmer is ten times more productive than an average programmer. A great programmer is 20-100 times more productive than the average. This is not an exaggeration – studies since the
Read more