Geek Answers Handbook

What should I do with the supplier catalog regarding subversion?

So I have a problem. I checked in my frozen gems and rails, although you should not do this. I figured it was easy and wouldn't be that important. Well, later I updated the rails and at the same time deleted all the .svn files in the suppliers / rails directories. I heard that what I really need to do is just do something with svn: externals in my provider directory. What exactly do I need to do, and will capistrano use my frozen gems if they are not in my repo? If he will not use my frozen gems, how can I recover these .svn files correctly, because this will happen again.

Thanks!

+5
source share
4 answers

  • To recover deleted directories .svn, run svn update. They will be back.

  • I just check the exported gems. I'm using the gem unpack <gemname>catalog vendor/gemsand svn addand committhere.

  • Anything in vendor/pluginsor vendor/railsI'm tracking piston usage. For example, this is how I get the rails:

    % piston import http://dev.rubyonrails.org/svn/rails/tags/rel_2-0-2/ vendor/rails

To use the piston gem install piston.

Note. I need to find another / better solution for replacing the piston, as Rails continues to use git and cannot update the subversion repository.

+3
source

Piston .

+4

svn: externals

  • , svn

  • , , svn ?

- .

+2

: Ruby/Rails, , ( , ), Subversion.

.svn "Subversion" bookkeeping. .

.svn . .svn - subversion (, ), , svn, .

.svn, svn.

svn: externals " ". Project A Project B, Project A. , svn: external, Project A, , Project B, Project A . , "thirdparty", , evn: subversion.

One of the tips to solve such version problems is to have separate release directories for libraries (or frozen gems), and in your projects that need them, use the svn: external link for the appropriate release directory. As new releases become available, simply change the svn: external property to point to the new release directory and svn update.

+1
source

More articles:


All Articles