I appreciate the feedback. Like many things changing one thing, forces
changes in others. Our build system uses files from several projects
within our repository and we also keep the local structure on
developer's systems fixed so that our build system and installers will
be able to find the files consistently.
So basically much of my annoyance came down to having checked out the
root of our repository. Now I have a structure that is mirrored from the
repository but only select folders are actually checked out. This has
given me the flexibility I want.
Thanks again.
Sincerely,
Glenn Welker
Developer
MRH Technology Group
www.mrhtech.com
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2006Q1@ryandesign.com]
Sent: Tuesday, February 21, 2006 2:09 PM
To: Glenn Welker
Cc: users@subversion.tigris.org
Subject: Re: Updates and tags
On Feb 21, 2006, at 14:22, Glenn Welker wrote:
> I am trying to determine the best way to update my local files without
> pulling down every tagged project.
Do not check out the project's directory from the repository.
Instead, check out the project's trunk, and also any branches you're
working on. Do this for each project you're working on. To update,
switch into each working copy and update. If this is tedious, you can
write a script which does it for you, though, really, why would you need
to update all working copies at once? Just update the ones you're going
to work on today.
To make a branch or a tag, use URLs to the repository; do not make the
branch or tag by copying things in your local working copy. Not that
there would be anything wrong with doing so, but doing so would require
you to have checked out the project's root directory, which as you're
discovering is inefficient and not really the best way to do it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 21 23:01:10 2006