smaller working-copies (was compressed or no text-base)

Hello everybody,

there have been some discussion in the past how to get a smaller working-copy.

Links are
        http://marc.theaimsgroup.com/?l=subversion-dev&m=105311561626396&w=2
                compressed text-base (zlib), is issue 908
                        http://subversion.tigris.org/issues/show_bug.cgi?id=908
        http://marc.theaimsgroup.com/?l=subversion-dev&m=103578782825114&w=2
                no text-base, is issue 525
                        http://subversion.tigris.org/issues/show_bug.cgi?id=525
and related too
        http://marc.theaimsgroup.com/?l=subversion-dev&m=104849632010219&w=2

Now I'd like to know the current status of this discussion and/or possible
patches. I saw that both are registered as "Post 1.0" - but when is 1.0
planned, and when may this arrive??

I'm asking because my developers have each about 1GB data, therefore about 1GB
text-base. If it's possible to have no text-base it's a lot better for
performance, as the repository is on the same machine, and the file-cache
would not trash as much.

I'd be most grateful if somebody had a patch lying around for issue 525 -
possibly against subversion 0.25 when that comes around.

Alternatively I thought about making hardlinks of the files in the
.svn/-directories. AFAIK makes the lib_wc always a temporary file which is
then moved - right? so using hardlinks in the .svn-directories should not
hurt - right?

I don't trust the various editors, or I'd even hardlink the wc-files ... but
if an editor just writes to the file without deleting it (or using a
temporary file), it get's changed in every wc ...

Any suggestions? Help, please??

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 10 11:17:09 2003