Menu
Got a (hopefully small) question regarding SVN and checking out repos. Basically I see conflicting tutorials and suggestions regarding what to check out and when. Some will say:
svn co http://my.repos.com/project my_project
…while others say:
svn co http://my.repos.com/project/trunk my_project
When would I want to grab the trunk directly vs the entire project? In the past I've never had trouble with either, but I'm not sure if there are scenarios where one is preferable to the other.
Best.
590
ADVERTISEMENT. ADVERTISEMENT. The Checkout command is used to copy the files from the SVN repository to the working copy. If we want to access files from the SVN server, then we have to check out it first. The checkout operation creates a working copy of the repository where we can edit, delete, or add contents.
By checking out files from a Subversion repository, you obtain a local working copy of the repository, which you can edit. After making the necessary changes, you can publish the results by committing, or checking in your changes to the repository.
If you want to write a script which requires no input, you should use the official Subversion command line client instead. checkout a working copy in REV revision: svn checkout --revision REV https://svn.example.com/svn/MyRepo/trunk/ svn checkout https://svn.example.com/svn/MyRepo/trunk/@REV.
usually a subversion repository has 3 main directories :
Trunk is for the most up to date branch of the code.
Branches are usually created in order to develop a specific feature that you do not yet want in the trunk.
Tags are like save-points of the trunk.
If you do a checkout at the root of the project, you will get all the branches, all the tags and the trunk. This can lead to a huge amount of data.
For example, if each code release is tagged, you will get the source code from all your past releases !
I hope this will help you
Jerome Wagner
184
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
