* Branko ??ibej wrote (2005-07-17 12:51):
>Thorsten Haude wrote:
>>>3. Why not just set 'store-passwords = no' in ~/.subversion/config?
>>This would make deployment more difficult. A patched version would be
>>a simple binary install using whatever package manager we prefer at
>>the moment. Also, I found at least two versions of the default config
>>file, so patching the config automatically would not be easier.
>Note that you can do the same in /etc/subversion/config as a global
>default, which is probably easier to deploy than changing the default
>config for every user.
That might be an option. I can't find anything on this file in the
online book, could you point out where to find documentation for this?
>>Any ideas about my original questions? Would the patch work?
>Don't know; have you tested it?
Yes, I did a check and the password was not saved. Still, I can't be
sure that it does what I want until I get a much better view on the
internal structure. I hoped one of the more experienced developer
could quickly verify it or point out a better way to achieve this.
>>Is there a better way?
>If you really have to patch Subversion, it would be better to tweak
>svn_config_ensure so that it writes "store-passwords=no" into the
>default ~/.subversion/config file.
Indeed, that seems to be much simpler. Thanks for the tip!
>>Is there a way to disable client credentials caching
>Yes, there is a way to disable credentials caching. The question is, do
>you really want to maintain your own fork of the SVN code indefinitely?
Not at all. There seems to be no option though if we don't want to
deal with the current irritating default.
There are two major products that come out of Berkeley: LSD and UNIX.
We don't believe this to be a coincidence.
- Jeremy S. Anderson
Received on Thu Jul 28 22:09:45 2005
- application/pgp-signature attachment: stored