The problem is subversion doesn't have control over when a file is
modified and therefore can't enforce the copy-on-write. Any user with
any application (text editor, build tool, IDE, script) is going to come
along and simply modify the files because they exist in a normal
filesystem. At that point, it is too late to copy the original to
create the text-base.
I think svk deals with this by creating a local svn *repository* and
then creating a bare WC that doesn't need a text base. Because the
repos is local, it can throw out the normal svn policy of reducing
server/client communications and request a full copy from the local
repos when doing diffs/deltas between repos versions and wc versions.
But then you have a local repos, which takes space.
The only other way to deal with this would be to enforce controlled
access to the wc. Since all tools (IDE, text editors, etc.) are used to
dealing with a regular filesystem, you'd have to build a virtual
filesystem wc that did copy-on-write. But that's a whole different project.
Cheers...
Bruce
Jan Hendrik wrote:
>
> Being about 1000 messages behind in reading user list I get one
> thing from this awful thread out of this message/reply:
>
> Is a textbase necessary for any SVN operation *as long as the file
> in the working copy has not been changed*? In other words
> Wouldn't it be possible/an option that textbase is just and only
> created when the original file is saved and cleared after the next
> commit? I suppose there would have to be a background process
> to take care of this.
>
> Just a little idea of mine.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 15 17:14:12 2004