You should have a look at YAM. I completed basic SVNFS read capability
yesterday. (Using FUSE for the userland filesystem frontend, and the
python bindings as the repository access backend).
See
http://zerowing.idsoftware.com/yam/
http://zerowing.idsoftware.com/yam/YAM_200_2e1_2e2_20Design
Note that we are *always* looking for developers, contributors, etc.
TTimo
On Wed, 06 Oct 2004 20:12:56 -0700
Karl Chen <quarl@eecs.berkeley.edu> wrote:
>
> Hi, I am thinking about writing a file system for Linux that
> transparently use a Subversion repository or working copy. Since
> this will do a lot of extra commits, I think the "Eric goes to
> lunch"/svk distributed model will work well together when editing
> source code. It will transparently add useful versioning to many
> applications (without needing svk-type two-layer version control).
>
> Comments/suggestions?
>
> Example command-line usage:
>
> % svnmount http://svn.quarl.org/repos/foo ~/foo
> % cd ~/foo
> % diff -u main.C main.C@123 # like 'svn diff -r 123 main.C'
> % mv a.py b.py # like 'svn mv a.py b.py'
>
> Issues:
>
> - whether to automatically commit each action; this could be a
> run-time per-WC option
>
> - whether to automatically add or ignore a new file? e.g., object
> and temporary files should be ignored. Will the svn:ignore
> feature be good enough to handle this?
>
> - is it easy to arrange for 'cp a b' to be 'svn cp a b', if cp is
> implemented as 'cat a > b'?
>
> - how to support normal svn clients; perhaps instead of the mount
> above use:
>
> svn co http://svn.quarl.org/repos/foo ~/foo-wc
> svnmount ~/foo-wc ~/foo
>
> Without the intermediate WC, svnfs would have to operate in
> automatic-commit mode.
>
> For example, I have my /etc stored in a Subversion repository.
> But often this WC is manipulated by scripts that create, move,
> delete files, and I have to manually tell svn that and also
> commit; I would rather just have it be automatically versioned.
>
>
>
>
>
> --
> Karl 2004-10-06 19:48
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 8 10:20:33 2004