[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Need to adjust based on svn:execute

From: David Ripton <dripton_at_ripton.net>
Date: 2005-02-09 19:56:52 CET

On 2005.02.09 10:57:11 +0000, Ben Collins-Sussman wrote:
>
> On Feb 9, 2005, at 8:04 AM, David Ripton wrote:
>
> >On 2005.02.08 19:54:35 +0000, Buddy Burden wrote:
> >>Okay, here's the situation: My user's working copy is on a Linux box,
> >>where it has to be (it's a web site and the Apache server runs on
> >>Linux).
>
> Here's a better idea: have her create a working copy on local disk,
> rather than on a samba share. Then when she commits, have a
> post-commit hook update a *different* working copy on the linux box.

While this is of course the SVN-correct answer, web developers *hate*
this. They want to make a lot of little tweaks, testing each one
quickly as they go, then check in when they're done with the logical
task.

If you use the version control system as the sole means of delivering
files from the author's work space to the author's primary test space,
that means lots of extra little checkin steps that break the author's
flow. (They also leave really ugly version history with no checkin
comments, but that's secondary.)

It's comparable to a C programmer having to check in code before being
allowed to compile it.

IMO the only reasonable way to do web development is to put a web server
on every developer's local machine. (Of course, you still also want the
shared ones, for integration and more testing. And the hook script
is a good idea there.)

-- 
David Ripton    dripton@ripton.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 9 19:59:02 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.