Thanks for the tips. These responses help me picture things differently
than I have been and I think I am actually on the right track now.
Thanks all who responded,
Alexis
-----Original Message-----
From: John Peacock [mailto:john.peacock@havurah-software.org]
Sent: Monday, October 01, 2007 12:13 PM
To: Turner, Alexis (GPG)
Cc: users@subversion.tigris.org
Subject: Re: Best practice, working copy and repository
Turner, Alexis (GPG) wrote:
> C:\repository>svn info
> svn: '.' is not a working copy
>
> D:\Web>svn info
> Path: .
> URL: svn://localhost/branches
> Repository Root: svn://localhost
Yeah, that's fine. Your repository is c:\repository and your checked
out working copy is in D:\Web and consists of everything under /branches.
I suspect what you have is just a very poorly organized repository, with
way too many projects lumped together, which is why it appears you have
*everything* checked out on D:\Web. I suggest you read through the
SVNBook as a whole, especially this section:
http://svnbook.red-bean.com/en/1.4/svn-book.html#svn.branchmerge.maint.layou
t
It's not too late to reorganize your repository along more sane lines;
it is merely a matter of a lot of 'svn mv' commands to move everything
around (and you can even do it one project at a time if you like). You
may find it easier to manage if you check out the root of your
repository tree
svn co svn://localhost/ d:\reorg
and then cd into reorg and use 'svn mkdir' and 'svn mv' to reorganize
things. Then you can commit in chunks (e.g. at the project level) to
keep things organized.
One other thing I'd suggest is that if you are running multiple websites
out of the same repository that you check out each site independently of
the others, even if all sites are still peers in the repository. What I
mean is that D:\Web will no longer contain a working copy of /branches,
but will instead contain a number of working copies, each containing a
single project, ala
D:\Web\Project1 => /branches/project1
D:\Web\Project2 => /branches/project2
etc. This makes it much easier to remove website files from the
webserver without having to remove them from the repository. It also
makes it less confusing if you move a single site to a different branch
during development.
HTH
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 1 19:13:11 2007