Re: svn checkout crush on mapped samba share from windows client

Alexxoid wrote:
> This is a not acceptable choice for me, because we are using linux
> server as the development server -- it includes apache + php
> applications.

Then you should have said that before, so I could given you the "correct" answer
the first time. ;-)

The development server should have it's own working copy, that you are not
sharing with a workstation. You should never share working copies between
people or machines, because it can confuse you when you try and commit changes.
 Every working copy should be "local" and unique to that person/process.

The development model I used at my last job was to have the developers write
code and commit changes (often) on their own boxes, usually to trunk. Then a
post-commit hook which would keep a test server in sync with the repository.
Then when a particular page or feature was complete, a tag would be created from
trunk, which would cause the production server to automatically be updated (from
the same post-commit script).

I even wrote a tool to make this trivially easy:

        http://search.cpan.org/search?query=SVN::Notify::Mirror
        http://search.cpan.org/search?query=SVN::Notify::Config

The second link is to a module I didn't write originally, but which I now
maintain. It makes this sort of automation completely painless.

John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-29 02:45:05 CET