On Fri, Dec 23, 2016 at 08:06:38AM +0100, Andreas Krey wrote:
> On Thu, 22 Dec 2016 13:48:47 +0000, Stefan Sperling wrote:
> > Since each .svn dir lives in a separate working copy its path is not a
> > global system setting.
>
> A safer alternative would be to look, when in /home/ak/some/wc, for
>
> /home/ak/some/wc/.svn
> /home/ak/some/.svn.wc
> /home/ak/.svn.some.wc
> /home/.svn.ak.some.wc
> /.svn.home.ak.some.wc
>
> or with an envvar SVNDIRS=/home/ak/svndirs
>
> /home/ak/some/wc/.svn
> /home/ak/svndirs/.svn.home/ak/some.wc
I agree that such a scheme would be neat and predictable. Thank you!
Having the env var point to a parent dir of .svn dirs seems like a
good enough solution to the problem I see with the original proposal.
> > I think the use case described would be much better served by implementing
> > support for a shared .svn dir located e.g. in the user's home directory which
> > can then be shared by multiple working copies.
>
> This, incidentallly, is also *much* more complex to implement, beginning
> with the problem that you can no longer just throw away a working copy
> and its .svn directory, and ending with two users accessing a WC that
> will now look into two different places for the .svn dir.
Well, at the time the wc-ng effort was started, a centralized .svn was
one of the design goals. That's why the DB schema is the way it is.
It's just too bad that work on these grand ideas has not been finished.
I am probably being a bit cynical because, to be honest, I don't expect
anyone will pick up and finish the task at this point.
Received on 2016-12-23 09:31:24 CET