comment on

Short example of how to start out with subversion (honestly, if you're just starting out I don't see merit in beginning with one of the older version control systems, they're no easier to learn and make your daily life harder).

Let's say your current code is in /home/neversaint/code and you'd like to keep the subversion repository (the backend storage, i.e. database if you will) in /home/neversaint/subversion.

svnadmin create /home/neversaint/subversion
[download]

This will create an empty repository for you.

cd /home/neversaint/code
svn import . file:////home/neversaint/subversion
[download]

This will import your codebase into the repository.

mkdir /home/neversaint/workspace
cd /home/neversaint/workspace
svn co file:///home/neversaint/subversion
[download]

This will create a new copy of your current codebase in /home/neversaint/workspace. From then on, make all changes to these files. Whenever you want to save your files to the repository, do a

svn -m "Commit message" ci
[download]

This will update the repository to the state of the workspace.

For further instructions, see the book pointed out by duff and the subversion documentation, execute

svn help
[download]

and

svn help <command>
[download]

for details on certain commands.
Update:Changed to using real-world paths, after msg's asking for clarification, also fixed a syntax error in the create.

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan

In reply to Re: Learning How to Use CVS for Personal Perl Coding Practices by tirwhan
in thread Learning How to Use CVS for Personal Perl Coding Practices by neversaint

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks