Re: svn commit: r1869868 - /subversion/trunk/INSTALL
On 16.11.2019 00:41, Daniel Shahaf wrote: > hartmannat...@apache.org wrote on Fri, Nov 15, 2019 at 16:21:00 -: >> +++ subversion/trunk/INSTALL Fri Nov 15 16:20:59 2019 >> @@ -120,17 +120,17 @@ I.INTRODUCTION >> assembler modules of OpenSSL. As of OpenSSL 1.1.0 NASM is the >> only supported assembler. >> >> + * Berkeley DB (DEPRECATED and OPTIONAL for client and server) >> >> + When you create a repository, you have the option of >> + specifying a storage 'back-end' implementation. Currently, >> + there are two options. The newer and recommended one, known > There are three options: bdb, fsfs, fsx. (This error predates your change.) FSX is still experimental, is not tested by buildbots, was never "released" in an meaningful way and now I doubt it ever will be. -- Brane
Re: svn commit: r1869868 - /subversion/trunk/INSTALL
hartmannat...@apache.org wrote on Fri, Nov 15, 2019 at 16:21:00 -: > +++ subversion/trunk/INSTALL Fri Nov 15 16:20:59 2019 > @@ -120,17 +120,17 @@ I.INTRODUCTION > assembler modules of OpenSSL. As of OpenSSL 1.1.0 NASM is the > only supported assembler. > > + * Berkeley DB (DEPRECATED and OPTIONAL for client and server) > > + When you create a repository, you have the option of > + specifying a storage 'back-end' implementation. Currently, > + there are two options. The newer and recommended one, known There are three options: bdb, fsfs, fsx. (This error predates your change.) Cheers, Daniel > + as FSFS, does not require Berkeley DB. FSFS stores data in a > + flat filesystem. The older implementation, known as BDB, has > + been deprecated and is not recommend, but is still available. > + BDB stores data in a Berkeley DB database. This back-end > + will only be available if the BDB libraries are discovered at > + compile time. > >* libsasl (OPTIONAL for client and server) > > >
svn commit: r1869868 - /subversion/trunk/INSTALL
Author: hartmannathan Date: Fri Nov 15 16:20:59 2019 New Revision: 1869868 URL: http://svn.apache.org/viewvc?rev=1869868=rev Log: INSTALL: Rewrite section about Berkeley DB dependency. * INSTALL: ("Dependencies in Detail" -- "Berkeley DB") Add "DEPRECATED" to the title of the bullet point. Rewrite the paragraph to (hopefully) make it more clear. Rationale: Avoid having to read a long paragraph only to find out at the end that BDB is deprecated. Modified: subversion/trunk/INSTALL Modified: subversion/trunk/INSTALL URL: http://svn.apache.org/viewvc/subversion/trunk/INSTALL?rev=1869868=1869867=1869868=diff == --- subversion/trunk/INSTALL (original) +++ subversion/trunk/INSTALL Fri Nov 15 16:20:59 2019 @@ -120,17 +120,17 @@ I.INTRODUCTION assembler modules of OpenSSL. As of OpenSSL 1.1.0 NASM is the only supported assembler. - * Berkeley DB (OPTIONAL for client and server) + * Berkeley DB (DEPRECATED and OPTIONAL for client and server) - There are two different repository 'back-end' - implementations. One implementation stores data in a flat - filesystem (known as FSFS); the other implementation stores - data in a Berkeley DB database (known as BDB). When you - create a repository, you have the option of specifying a - storage back-end. The Berkeley DB back-end will only be - available if the BDB libraries are discovered at compile - time. The Berkeley DB back-end has been deprecated and - is not recommend. + When you create a repository, you have the option of + specifying a storage 'back-end' implementation. Currently, + there are two options. The newer and recommended one, known + as FSFS, does not require Berkeley DB. FSFS stores data in a + flat filesystem. The older implementation, known as BDB, has + been deprecated and is not recommend, but is still available. + BDB stores data in a Berkeley DB database. This back-end + will only be available if the BDB libraries are discovered at + compile time. * libsasl (OPTIONAL for client and server)