On Jan 28, 2008 10:27 PM, Ryan Schmidt <subversion-2007b_at_ryandesign.com> wrote:
>
> On Jan 28, 2008, at 19:37, John Peacock wrote:
>
> > 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.
>
> [snip]
>
> He didn't say he was sharing a working copy. :) If he is sharing a
> working copy, then yes, he should stop that. But for example at the
> web design shop where I used to work, the developers also used
> Windows machines, and used TortoiseSVN to check out working copies
> onto Samba-mounted shares from a central Linux development server.
> These were private working copies for each developer, in their home
> directory on the Linux server. It worked. Something could be strange
> about Alexxoid's Samba setup that's preventing it from working for him.
Ah, but he is "sharing" a WC between OSes, and that *is* discouraged.
If you've got svn:eol-style set to native, and use TSVN to operate on
the WC via Samba on a Linux server, you're going to have DOS/Windows
line-endings on your Linux host, which would normally expect *nix line
endings. Then there's also the possible issues with permissions,
symlinks, etc.
---------------------------------------------------------------------
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 04:55:55 CET