"Miller, Eric" <Eric.Miller@amd.com> wrote on 12/03/2007 11:52:22 AM:
> > > I would really like to be able to implement a light-weight working
> copy
> > > using symbolic links that point to a common read-only area,
> replacing
> > > the links with editable data when locks/edit permissions are
> granted.
> > >
> > > Does anyone have any ideas if something like this is feasible in
> > > subversion?
> >
> > A common shared area is interesting, but probably hard to implement.
> > Think about permissions, who actually updates the common area, etc.
>
> I guess I was thinking that some sort of daemon or post-commit hook
> would take care of updating the common area. The real tricky part is
> handling mixed revisions and branches.
I thought of this as well, but didn't mention it. You could think
of it as a pristine working copy "cache".
Ultimately you could just contact the server and request the file
contents when you need them. Obviously this is exchanging network
bandwidth for disk space, which is exactly the opposite of the
original Subversion design to minimize network use at the expense
of disk space...
> > I believe someone thought about keeping the pristine files in a
> compressed
> > format. This might reduce the space at least a little, with the
> > possibility of not too many complex working copy code changes.
>
> I guess this would help incrementally depending on the type of data, but
> it doesn't help with duplication of the actual data.
>
> Guess I'm looking at something that is pretty far removed from svn's use
> model (again). It was a shot in the dark - thanks for the response!
I find some of our use cases painful as well, so you aren't alone!
Kevin R.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 3 19:03:02 2007