RE: [TSVN] Re: SVN for different setups?

I'm not sure I follow you.
The 'X' - is that the same as the 'KL' modules, for test _or_ prod?

Can you, or someone else, give an example of a script to handle this?
I can imagine having KL/test and KL/prod in a separate directory, and using
the script to copy one or the other to the right place in the working copy.
Is that roughly what you meant?

-----Original Message-----
From: Jens Scheidtmann [mailto:Jens.Scheidtmann@bayerbbs.com]
Sent: den 26 juli 2004 10:31
To: dev@tortoisesvn.tigris.org
Subject: [TSVN] Re: SVN for different setups?

"Jan Bergquist" <jb.bergquist@telia.com> writes:

[...]
> Most of the code, say 10 modules (A-J), are identical for test and
> production.
> For test vs production 2 files (say K and L) have to be slightly
different.
> They are rarely changed.
>
> I need to set up my working copy for testing (A-J and KL/test).
> When this is ok, I need to distribute the new versions (A-J and KL/prod)
to
> the 'real' web site, via FTP.
[...]

I would do it like this:

- Have 10 + 2 + 2 + X files in the working copy.
- write scripts which handle KL/test and KL/prod depending on the
  build target (ant, make, whatever --- that would make up the X).
- Tag a new version before upload to prod.
- Do a clean checkout of the newly tagged version.
- Upload the newly checked out version to prod.

HTH,

Jens

--
Jens.Scheidtmann@bayerbbs.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org