Is there an environment variable that can be used to specify the location of
the .svn directory ?
If not, is this planned for a future version ?
Thanks !
Hello Hugh,
> Is there an environment variable that can be used
> to specify the location of the .svn directory ?
The only method to alter the .svn path (that I am aware of) is the the
SVN_ASP_DOT_NET_HACK
http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.wc
>
On 21.12.2016 10:48, Andreas Stieger wrote:
> Hello Hugh,
>
>> Is there an environment variable that can be used
>> to specify the location of the .svn directory ?
> The only method to alter the .svn path (that I am aware of) is the the
> SVN_ASP_DOT_NET_HACK
> http://svnbook.red-bean.com/nightly/
On 21.12.2016 17:57, Miller, Hugh wrote:
>> What is the problem you are trying to solve?
> The context is versioning file sets/trees that are used by other applications
> and processes. In this situation, it is nice or imperative to be able to
> treat the file set/tree as just the original, but s
Branko Čibej wrote on Thu, Dec 22, 2016 at 11:03:27 +0100:
> On 21.12.2016 17:57, Miller, Hugh wrote:
> >> What is the problem you are trying to solve?
> > The context is versioning file sets/trees that are used by other
> > applications and processes. In this situation, it is nice or imperative t
On Thu, Dec 22, 2016 at 11:47:41AM +, Daniel Shahaf wrote:
> Allowing to specify the location fo the .svn dir through a --option or
> envvar does not require sharing .svn dirs amongst different working
> copies.
>
> The only code change that should be needed is a short-circuit codepath
> in th
On Thu, Dec 22, 2016 at 1:48 PM, Stefan Sperling wrote:
> 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 would work without an env va
On Thu, Dec 22, 2016 at 01:52:01PM +0100, Olaf van der Spek wrote:
> On Thu, Dec 22, 2016 at 1:48 PM, Stefan Sperling wrote:
> > 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
On Thu, 22 Dec 2016 13:48:47 +, Stefan Sperling wrote:
...
> I think this idea is short-sighted. I can imagine this suggestion to cause
> major inconvenience if implemented.
I know of a VCS having done exactly this.
> Inevitably, an environment variable will point to a .svn directory of one
>
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
>
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 .s
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
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 do
On Fri, 23 Dec 2016 13:22:03 +, Olaf van der Spek wrote:
...
> > (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
On Sun, Dec 25, 2016 at 12:06 AM, Andreas Krey wrote:
> On Fri, 23 Dec 2016 13:22:03 +, Olaf van der Spek wrote:
> ...
>> > (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 m
Olaf van der Spek wrote on Sun, Dec 25, 2016 at 09:59:44 +0100:
> Aren't you covered if you search * instead of . ? AFAIK * excludes dot
> files too.
That excludes _all_ dot files, not just .svn, and doesn't ignore .svn
dirs in nested working copies (such as externals).
I mentioned hidesvn(1) upt
> -Original Message-
> From: Branko Čibej [mailto:br...@apache.org]
> Sent: Wednesday, December 21, 2016 5:30 AM
> To: users@subversion.apache.org
> Subject: [**EXTERNAL**] Re: environment variable for location of the .svn
> directory ?
>
> On 21.12.2016 10:4
17 matches
Mail list logo
