On Fri, 17 Jan 2025 07:03:34 +0100, Daniel Sahlberg
<daniel.l.sahlb...@gmail.com> wrote:

>I agree with Bo here although I don’t understand enough about recent
>Linux-on-the-desktop development. A long time ago, setting DISPLAY was the
>way to declare where you wanted to your GUI to appear. When SSH-ing into a
>box you wasn’t able to set DISPLAY to the X server of that computer. It was
>either empty or you could forward it back to your local computer. When
>running X directly on the console, DISPLAY was obviously pointing at
>localhost. There are no guarantees that the same uses logged in on the
>local console as the one running the ssh session.
>
>But we are running very much off-topic here. From a Subversion perspective
>we are just asking the password manager to get the password and then it is
>out of our hands.

Thanks for the explanation!

Follow-up question then:

How do I configure svn out-of-the-box in order for it to use a password manager
that communicates via the command line rather than any existing GUI desktop.
As it is now on my newly installed RPi4 I have not modified anything in the
config or servers files.

And it states this: 
------------------------------------------------------
$ svn --version:
svn, version 1.14.2 (r1899510)
   compiled Jan 31 2023, 18:14:10 on aarch64-unknown-linux-gnu
...
The following authentication credential caches are available:

* Plaintext cache in /home/bosse/.subversion
* Gnome Keyring
* GPG-Agent
* KWallet (KDE)
-------------------------------------------------------

I assume that the last 3 alternatives are Desktop dependent and use GUI dialog
boxes?

I'd appreciate it to get a specific direction as to which items to add/change in
the default files in $HOME/.subversion/: config and servers, in order for the
passwords to be cached in a text-only environment.
I.e. how to set them to use a command line interface only?

If that is achieved I will add it to my Subversion how-to document and not ask
again....


-- 
Bo Berglund
Developer in Sweden

Reply via email to