Re: environment variable for location of the .svn directory ?
On Fri, Dec 23, 2016 at 08:06:38AM +0100, Andreas Krey wrote: > On Thu, 22 Dec 2016 13:48:47 +, 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.
Re: environment variable for location of the .svn directory ?
On Fri, 23 Dec 2016 09:30:45 +, Stefan Sperling wrote: ... > 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. See, I thought, wc-ng was done, with the single .svn directory (modulo externals). Having .svn outside the worktree isn't relevant for me; my gripe with .svn is that the pristine copies aren't compressed and thus generate matches in 'find | xargs grep' (in the nonexistence of 'svn grep'). Andreas -- "Totally trivial. Famous last words." From: Linus Torvalds Date: Fri, 22 Jan 2010 07:29:21 -0800
Re: environment variable for location of the .svn directory ?
Andreas Krey wrote on Fri, Dec 23, 2016 at 11:56:40 +0100: > On Fri, 23 Dec 2016 09:30:45 +, Stefan Sperling wrote: > ... > > 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. > > See, I thought, wc-ng was done, with the single .svn directory > (modulo externals). That was another design goal. wc-ng *already uses* one .svn dir per working copy (modulo externals), and the schema *supports* one .svn for multiple working copies (even of different repositories). > Having .svn outside the worktree isn't > relevant for me; my gripe with .svn is that the pristine > copies aren't compressed and thus generate matches in > 'find | xargs grep' (in the nonexistence of 'svn grep'). Some greps accept a «--exclude='*.svn-base'» option. There's a tool called 'hidesvn' which uses LD_PRELOAD so you can do «hidesvn grep -R foo» and it won't recurse into .svn dirs. (You could alias grep to one of the above solutions so hidesvn or --exclude are always used, they're both harmless when not in a working copy.) ag(1) and friends ignore .svn by default. Cheers, Daniel
Re: svnserve poor commit performance
Jakub Petr wrote on Thu, Dec 22, 2016 at 10:28:24 +0100: > Why the "transmitting phase" should take so long? Usually it's because of virus scanners intercepting the disk operations (opening/writing files). What makes you think the slowness is svnserve's fault? Is the commit faster over file:// than over svn://localhost?
Re: environment variable for location of the .svn directory ?
On Fri, Dec 23, 2016 at 11:56 AM, Andreas Krey wrote: > On Fri, 23 Dec 2016 09:30:45 +, Stefan Sperling wrote: > ... >> 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. > > See, I thought, wc-ng was done, with the single .svn directory > (modulo externals). Having .svn outside the worktree isn't > relevant for me; my gripe with .svn is that the pristine > copies aren't compressed and thus generate matches in > 'find | xargs grep' (in the nonexistence of 'svn grep'). Don't find or grep have options to ignore dot / hidden files? -- Olaf
