>=?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <firstname.lastname@example.org> writes:
>>Turns out this is a faq:
>>*An ENOMEM error is returned from DB_ENV->open
>><http://www.sleepycat.com/docs/api_c/env_open.html> or DB_ENV->remove
>>Due to the constraints of the PA-RISC memory architecture, HP-UX does
>>not allow a process to map a file into its address space multiple times.
>>For this reason, each Berkeley DB environment may be opened only once by
>>a process on HP-UX; that is, calls to DB_ENV->open
>><http://www.sleepycat.com/docs/api_c/env_open.html> will fail if the
>>specified Berkeley DB environment has been opened and not subsequently
>>Opening an environment more than once is exactly what we do in
>>svn_ral_local__split_URL. We either have to get rid of that function,
>>keep a list of currently open DB's around, or not work on HP-UX.
>>(Actually, since we don't support cross-repository copies, we knoy have
>>to remember the URL of the laready-open repo. Which makes sense, because
>>then we can just do a strncmp on the URL next time we try to open it,
>>instead of jumping through hoops the way we do now.)
>I think that once we have storage of canonical repos URLs in our
>entries files (soon to occur), svn_ra_local__split_URL() won't be
>used quite as much. It still must exist, as there are times (import)
>when there are no entries files to read.
Yes, that's what I'm counting on. :-)
However, I think we it'll turn out that having is list of open
repositories would be a good thing in the long run, anyway (think
>Of course, we *could* just change any subcommands that today use
>REPOS_URLs to instead use both a REPOS_URL (that is, a canonical repos
>URL, like http://svn.collab.net/repos/svn) and a REPOS_PATH (like
>trunk). I certainly *hope* we don't do such a thing, though.
No no no no no! That would be horrible!
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Apr 19 19:54:42 2002