[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: importing a new tree over an existing versioned copy

From: Jon Daley <tortoise_at_jon.limedaley.com>
Date: 2007-06-15 13:38:36 CEST

On Fri, 15 Jun 2007, Roel Vanhout wrote:
> I keep all libraries that I use (e.g., boost) in subversion so that it's easy
> to set up a dev environment with one checkout. How can I, when a new release
> of such a library is made, easily 'upgrade' my existing versioned copy?
> Changed files can be overwritten by copying the new version to a fresh
> checkout, but if some files were deleted in the new release, they will stay
> in the versioned copy and I don't see an easy way to recursively list all
> files that should be deleted from the repository because they're no longer in
> the library. Any ideas? Thanks.

         Do you mean "checkout"? If you do, you should do an update
instead of checkout, which would handle the deletes for you. If you are
doing a "checkout", you must be deleting the directory first, because svn
wouldn't let you checkout on top of an existing .svn directory, right?
         We have a similar thing as you (I think) and the developers just
do updates, and then our release process does an "export" to remove the
.svn directories.

To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Jun 15 13:38:43 2007

This is an archived mail posted to the TortoiseSVN Users mailing list.