On 10/13/06, Phyrefly <firstname.lastname@example.org> wrote:
> > svn update updates the current working copy. Wherever you've checked
> > out the directory from, it goes back to that URL and pulls down
> > updates from there. So if you check out a single project out of 500
> > in one repository, then svn up run from within that one project's
> > working copy will only update that project.
> You're not getting me. I have a development environment, which is a
> working copy of the whole repository.
Could you describe how do you intend to tag releases? Usually a working
copy contains only the trunk, or a single tag or branch.
I have a post-commit hook which does an update on the dev environment.
If that one repo covers the whole collection of projects, it'll be
> huge. Is there a way to pick up which folder has been commited, and
> do an update from just that path (within the hook script)? If not, I
> may have to split my repo up after all.
You're assuming that a working copy is a complete copy of the repo HEAD
revision. I don't know anyone who has their svn repo setup that way. When a
wc is created via a checkout from, say svn:\\svnserver\code\project1\trunk\,
the wc stores this path and "svn update" pulls updates to only that path in
Received on Fri Oct 13 16:27:33 2006