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

Re: "Export" to remote location - how?

From: Jan Eri <jan.eri_at_protector.no>
Date: 2005-06-25 20:25:19 CEST

Jan Eri wrote:
> But I have started to consider another way that
> may work even better in our case. I have discovered post-commit hooks,
> and based on an idea I heard I am wondering if it is possible to do
> something like this:
> 1. Have all my projects in separate directories in one svn repository
> 2. Establish my www test-sites as working copies of the repositories
> 3. Have a tag directory in every svn project directory
> 3. When creating a version that should be copied to the live site for
> testing or production, copy it to the tag-directory and commit
> 4. Use post-commit to update the working copy of the relevant project
> Is this possible? Any relevant sample code available?

I thought I had this under control with Bens pointer to

But I have discovered a problem when I perform a copy from my trunk to
the tags-directory that my live-site is a working copy of, tags/site1:

The first time works fine:
> svn copy trunk tags/site1
> A tags/site1

But the second time, when 'site1' already exists:
> svn copy trunk tags/site1
> A tags/site1/trunk

in other words copy assumes that I do not want to overwrite, and instead
adds directory trunk to site1 - which is not what I want. How should I
handle this better?

It seems a bit strange that the same command gives different results
like this.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jun 25 20:27:18 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.