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

[Fwd: Re: Avoid pristine copies]

From: Paul DeMarco <paul_at_pauldemarco.com>
Date: 2005-01-24 01:45:47 CET

  You could always use export, but that doesn't allow updates, or
additional exports, have to remove the folder and export again. So that
may be an option, if your not changing the source, if the working copy
is very large the following may also be an option:

have a svn wc on a server somewhere, run updates or switches, which are
both efficient, so that it looks like how you want the clients to have.

then if they are nix clients, run an rsync (with a pattern to ignore the
.svn folders), between the server wc and the client copy, it will at
least be fast.

could probably get a windows port of rsync as well, i dunno if that
exists (could always do it under cygwin, but thats probably un-needed
deployment complexity).

--paul

kfogel@collab.net wrote:

>Konstantin Scheglov <konstantin.scheglov@gmail.com> writes:
>
>
>> I want to use SVN for receiving updates for our internal software
>>products on user computers. But with SVN I have problem - it always
>>creates pristine copy of working directory. Is there any flag/way to
>>avoid this? I will never need to commit, only checkout, status, update
>>and may be switch.
>>
>>
>
>No way yet, sorry.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
>

attached mail follows:


Message-ID: <41F3456D.60507@pauldemarco.com>
Date: Sun, 23 Jan 2005 01:34:21 -0500
From: Paul DeMarco <paul@pauldemarco.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20050122)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: kfogel@collab.net
Subject: Re: Avoid pristine copies
References: <c9fa2f570501211159224a787c@mail.gmail.com> <85acr2tv58.fsf@newton.ch.collab.net>
In-Reply-To: <85acr2tv58.fsf@newton.ch.collab.net>
Content-Type: multipart/alternative;
 boundary="------------050301070008090907030605"

This is a multi-part message in MIME format.
--------------050301070008090907030605
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

You could always use export, but that doesn't allow updates, or
additional exports, have to remove the folder and export again, i think
this would work well though:

have a svn wc on a server somewhere, run updates or switches, which are
both efficient, so that it looks like how you want the clients to have.

then if they are nix clients, run an rsync (with a pattern to ignore the
.svn folders), between the server wc and the client copy, it will at
least be fast.

could probably get a windows port of rsync as well, i dunno if that
exists though.

--paul

kfogel@collab.net wrote:

>Konstantin Scheglov <konstantin.scheglov@gmail.com> writes:
>
>
>> I want to use SVN for receiving updates for our internal software
>>products on user computers. But with SVN I have problem - it always
>>creates pristine copy of working directory. Is there any flag/way to
>>avoid this? I will never need to commit, only checkout, status, update
>>and may be switch.
>>
>>
>
>No way yet, sorry.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
>

--------------050301070008090907030605
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=us-ascii" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
You could always use export, but that doesn't allow updates, or
additional exports, have to remove the folder and export again, i think
this would work well though:<br>
<br>
have a svn wc on a server somewhere, run updates or switches, which are
both efficient, so that it looks like how you want the clients to have.<br>
<br>
then if they are nix clients, run an rsync (with a pattern to ignore
the .svn folders), between the server wc and the client copy, it will
at least be fast.&nbsp; <br>
<br>
could probably get a windows port of rsync as well, i dunno if that
exists though.<br>
<br>
--paul<br>
<br>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:kfogel@collab.net">kfogel@collab.net</a> wrote:
<blockquote cite="mid85acr2tv58.fsf@newton.ch.collab.net" type="cite">
  <pre wrap="">Konstantin Scheglov <a class="moz-txt-link-rfc2396E" href="mailto:konstantin.scheglov@gmail.com">&lt;konstantin.scheglov@gmail.com&gt;</a> writes:
  </pre>
  <blockquote type="cite">
    <pre wrap=""> I want to use SVN for receiving updates for our internal software
products on user computers. But with SVN I have problem - it always
creates pristine copy of working directory. Is there any flag/way to
avoid this? I will never need to commit, only checkout, status, update
and may be switch.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
No way yet, sorry.

---------------------------------------------------------------------
To unsubscribe, e-mail: <a class="moz-txt-link-abbreviated" href="mailto:users-unsubscribe@subversion.tigris.org">users-unsubscribe@subversion.tigris.org</a>
For additional commands, e-mail: <a class="moz-txt-link-abbreviated" href="mailto:users-help@subversion.tigris.org">users-help@subversion.tigris.org</a>

  </pre>
</blockquote>
<br>
</body>
</html>

--------------050301070008090907030605--

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 24 01:48:14 2005

This is an archived mail posted to the Subversion Users mailing list.