On Feb 7, 2008 7:19 AM, Sven Süld <sven_at_trigger.ee> wrote:
> Andy Levy wrote:
> > On Feb 7, 2008 6:35 AM, Sven Süld <sven_at_trigger.ee> wrote:
> >
> > This should only happen if your WC lives on the Linux box and you
> > access it using TSVN, presumably via Samba. Sharing WCs between
> > developers and OSes is unsupported and can cause a number of problems,
> > the one you're experiencing being the least of it.
> >
> > If at all possible, maintain a WC and development environment on your
> > local workstation, and then have a separate WC on the Linux server for
> > compiling/testing/whatever you have to do there, using the repository
> > as the middleman in moving the files out to the Linux server.
> >
> This is of course completely different story. You are right about shared
> wc problems. But I disagree about developing on your own pc. This arises
> horde of new problems including OS problems, php/server conf problems
> etc etc.
Actually, local development (or each developer having their own WC on
the development server where they can code/test/debug) is a pretty
standard practice.
The Java web application I manage was initially developed by a
contractor working on MacOS and Linux, I can run it locally on XP, and
runs on both Win2K and Win2K3 servers in our environment. We have ZERO
"OS detection" routines in the application. We have OS- and
server-specific config files where appropriate to handle settings that
vary by those parameters and are applied when the application is
deployed, but we could have made them run-time if we wanted to give up
a little performance.
It *shouldn't* be hard to develop a cross-platform application that
runs on a "framework" (PHP) which already is cross-platform.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-02-07 14:41:27 CET