Pat Wenke wrote:
> Can our developers somehow "share" a working copy, so that none of us
> actually have to keep a local working copy?
>
This would, in part, defeat the purpose of using a revision management
system as your users would be sharing the login information, you
couldn't have multiple logins if they're sharing the same local copy.
If you want revision management control then your users will have to
adjust to having separate local copies. If each user adjusts to having
to work in a cleaner fashion (testing changes before committing, merging
changes as needed, planning what changes to make and communicating with
others regarding their intentions) then you won't have any problems.
> Once I commit a changed file to the repository, how do I get the
> updated version back into C:\www so it can be tested?
>
There are several ways, the best IMHO being to have another login for
the web server itself, then just checkout the files to the server as
needed. When code is known to be working just update the web server's
working copy.
> Now the repository contains this tree of data. Note that the original
> /tmp/project directory is unchanged; Subversion is unaware of it. (In
> fact,
> you can even delete that directory if you wish.) In order to start
> manipulating repository data, you need to create a new "working copy"
> of the data, a sort of private workspace. Ask Subversion to "check
> out" a working copy of the repository's trunk directory.
>
When you initially import a directory you do not have a Subversion
working copy and need to create one. Simply rename the old directory
(for a backup, helps beginners feel more assured that they're not going
to mess anything up) then checkout the project you want and start
working on /that/ working copy and not the original that you imported.
Test it with some random files until you feel comfortable with what is
going on.
> What this tells me is that after I import C:\www into the repository,
> I don't need it anymore. I understand that, and I understand creating
> a working copy, perhaps on my local machine, so that I can check out
> files and make changes, and that the changes get committed back to the
> repository. What I do not understand is to which directory should I
> point my IIS and CF roots, since C:\www is no longer needed.
>
The *files* in C:\www are no longer needed by Subversion so delete them
and then checkout your code to that directory.
--
*Damien McKenna* - Web Developer - dmckenna@thelimucompany.com
<mailto:dmckenna@thelimucompany.com>
The Limu Company - http://www.thelimucompany.com/ - 407-804-1014
"Nothing endures but change." - Heraclitus
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 21 16:39:44 2004