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

Re: Minimize the size a read-only working copy

From: B. Smith-Mannschott <bsmith.occs_at_gmail.com>
Date: Thu, 7 May 2009 12:32:16 +0200

On Thu, May 7, 2009 at 11:48, <webpost_at_tigris.org> wrote:
> I'm a beta tester for a software project written in Perl, in which I have no repository write ability.  Using SVN is convenient and minimizes the bandwidth and time needed for getting updates.  But at the expense of a lot of disk space.
>
> I have no need to ever revert changes or update to old revisions.  One of the things making the working copy so large are the .svn-base files.  Is there any way to operate without these files and still be able to do svn updates without them?

No.

You might be able to do something with the following ideas though:
svn export will give you a copy of the sources without .svn directories.
You'll need to make a note of the actual revision exported.
You can use svn diff to get the changes since your last update as a patch.
svn diff -rLAST_UPDATE:HEAD
And apply those with patch to your exported local copy using patch.
You'll need to keep track of which revision you're up-to-date with.
(LAST_UPDATE) for the next time you go get changes.
This probably won't work if there are renames and deletes.

Sounds like a pain.

// Ben

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2092970

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-07 12:33:16 CEST

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.