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

Re: Feature-Request

From: Gary Thomas <gary_at_mlbassoc.com>
Date: 2005-04-27 13:47:39 CEST

On Wed, 2005-04-27 at 13:43 +0200, Mark Morschhuser wrote:
> Hi,
> we have the following situation here:
> Our SVN-repository contains our project's sourcecode and the sourcecode from
> some 3rd party libs.
> Most of these 3rd party libs are CVS checkouts and we update them every month.
> Sometimes these libs delete files or add files which is a problem with our
> SVN, because files have to be added/deleted by hand.
> The only solution at this time is:
> a) svn del the lib-directories
> b) svn ci
> c) put the updatet sources in place
> d) svn add the lib-directories
> e) svn ci
> That's much work and it uses much more space in the repos (we had a 5GB-repos
> after a half year), because this method doesn't use diffs.
> A nice SVN-feature would be the following:
> "svn diffupdate <directory>" or something like that, which
> a) adds all files/directories within that directory that isn't inside the
> SVN-repos yet.
> b) deletes all files/dirs from the SVN-repos when they are not found within
> that directory any more
> There are some similarities to svn import, I guess.
> What do you think? Is it a good feature or is there a better workaround for
> situations like that? (ok, the easiest way would be not to include the 3rd
> party libs within our SVN-repos, but we have reasons to do so)
> Or maybe there still exists a tool that can do this?

This is just what the 'svn_load_dirs.pl' tool does quite well.

Read the section of the book on vendor branches as well.

Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 27 13:50:34 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.