Re: Subversion GUI client?

On Jan 23, 2005, at 11:11 PM, JC Hearn wrote:

> I don't follow you.
>
> Are you saying that "working copy on local file system" is a
> fundamental
> design concept of subversion? Why?

Because Subversion was designed to have a central server where the
repository is stored, and to have users have working copies
locally--optimizing for the common case in CVS where network access is
slow or limited, and users want to have copies locally.

> It seems to me that the working copy just needs to be in a different
> spot.
> Why insist that it be local? Why not check files out from a repository
> server to a development server, for example?

We don't *insist* that it be local, it's just the way we designed
Subversion to be used!

> It doesn't seem to me that the "local copy" concept would support web
> developers that well, unless I am completely missing something here.

Tens of thousands of CVS users have been doing it for *years*!

I know dozens of web developers who use Subversion every day with no
problems--they do all their work in a local working copy, and commit at
their leisure. When they're ready to update the production website,
they shell in to it and run 'svn update' in the working copy on the
webserver.

This is the model that tigris.org uses for Subversion, except that
commits to the www area of our repository get update automatically on
the server--no one has to have any access to the main server except for
Subversion access.

Some folks get fancy like this and keep the production site on a
branch, and merge changes to the branch when they're ready for
production. Then they have a cron job on the web server that updates
the branch on a regular basis.

-Fitz

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 24 07:22:05 2005