Geek Answers Handbook

Subversion large repository import / design

My normal workflow for creating a new repository with subversion is creating new repositories, checking the root of the repositories, creating tag tags for branches and connecting folders, and putting my initial files in the trunk. Then I commit this “initial import”, delete the uploaded repositories from my hard drive and do a boot check. Then I can start working.

However, when dealing with large imports, think that hundreds of megabytes and hosting for version control outside the site (based on http) this initial import may take quite a long time to complete. To make matters worse, after committing, I have to check out this massive trunk again.

Is there a way with subversion to use a local copy of the chest without checking again the data that already exists?

+5
source share
5 answers

There is - it is called "import in place" and it is described in the Subversion FAQ:

http://subversion.tigris.org/faq.html#in-place-import

What you really do is create a new empty project in the repository by checking the empty project of your local folder, which turns your folder into a working copy, and then adds all your (existing) files to this, 'so they are added to the repository when you are executing svn commit.

+12
source

" ", script TTB- ( ).

:

( ) , http (s), . , apache svnaccess (, ). , svn .

+3

"svn mkdir" // . , , .

+1

svn checkout --force "" . , .

: mkdir , "svnmucc", Subversion (, SlikSVN).

svnmucc .

+1
source

If you checked one folder, copied your files to it, run svn addand svn commit; You will not need to delete files and re-check.

Use the files in place: once they have been committed, as you described, they are ready to go.

0
source

More articles:


All Articles