Without looking at the code, my first guess would by that Subversion
is using svn_io_check_path() instead of svn_io_check_resolved_path()
when looking on disk for your auth cache. In other words, it isn't
trying to resolve your symlinks.
Henrik Holmboe <elements@hack.se> writes:
> Hello,
>
> I was just about to file a bugreport, but per the instructions at
> <http://subversion.tigris.org/project_issues.html> Im sending an email
> here to get some feedback.
>
> The issue Im having could be considered a bordercase by many. I have a
> special need to keep all secret data in special storage and therefore
> need to symlink the files stored in
> $HOME/.subversion/{svn.simple,svn.ssl.server}.
>
> When checking out a repository and permanently accepting the
> certificate and providing username and password the files in question
> are automatically created. I then move them to the other storage and
> create symlinks. The next time I issue a command that connects to the
> server, I am again asked questions as if the server was not already
> verified/authenticated.
>
> Please advise.
>
> .h
>
> --
> Henrik Holmboe, Stockholm, Sweden
> <http://henrik.holmboe.se/contact/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 18 22:56:29 2004