On Mon, May 19, 2008 at 5:21 AM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Sun, May 18, 2008 at 04:35:52PM -0400, Mark Phippard wrote:
>> The command line tests OK, although I notice that I now have to enter
>> my KWallet password on every command. Which seems kind of pointless.
>
> I didn't get this when I tested it briefly. I got one popup
> from kwallet asking for the wallet password.
> It didn't ask me ever again after that while running Subversion
> commands that require authentication.
I recall you tested around the same time I did. Arfrever sent an
email about making an additional change to disconnect the application
from the wallet after each command. I think that is what triggered
the change in behavior.
>> It looks like if I manually open my wallet then I get the chance to
>> say "Always Allow" and after that, while the wallet is open, I do not
>> have to enter it again.
>
> Hmm. Do you want me to check whether this was the case during
> my test as well? Note that I didn't play with any settings though,
> I assumed I was seeing the default behaviour.
>
> I cannot check right now though. I was using a friend's box that has
> KDE4 installed. It looks like he's not home atm and the box is turned
> off :/ But maybe it's back by the time I get your reply to this.
>
>> So it looks like if Subversion opens your wallet, then it also closes it.
>
> I don't understand what the implications of opening/closing the
> wallet are, but I guess Arfrever will know.
I suspect it is working the way Arfrever intended. I just want to be
sure. It seems like their will be a requirement for the user to
manually open their wallet to get decent behavior from the client.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-19 16:19:41 CEST