[
https://issues.apache.org/jira/browse/SVN-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Branko Čibej resolved SVN-2203.
-------------------------------
Resolution: Won't Fix
The BDB back-end is deprecated, so we won't add any new features to it.
> Subversion fs_base APIs usurp Berkeley DB config power.
> -------------------------------------------------------
>
> Key: SVN-2203
> URL: https://issues.apache.org/jira/browse/SVN-2203
> Project: Subversion
> Issue Type: Bug
> Components: libsvn_fs_base
> Affects Versions: 1.1.x
> Reporter: C. Michael Pilato
> Priority: Critical
> Labels: patch
> Fix For: unscheduled
>
> Attachments: 1_issue-2203-1.patch, 2_issue-2203-2.patch
>
>
> {noformat:nopanel=true}
> Berkeley DB allows you to specify programmatically and via DB_CONFIG
> alternative
> directories for database and logfiles used in a given environment (the
> "set_lg_dir" and "set_data_dir" directives). If you make use of such things
> in
> your Subversion repositories, most things work just fine. But any APIs which
> presume that logfiles or database files live in the environment directory are
> broken. One obvious example (svn_fs_berkeley_logfiles) comes to mind -- using
> 'svnadmin list-dblogs' or 'svnadmin list-unused-dblogs' on a so-configured
> repository will return bogus paths. There might also be problems with the
> hotcopy code, but I've not verified that.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
