rpm-5.4.16 snapshot

[Jeff Johnson]

On Mar 16, 2016, at 1:09 PM, Elan Ruusamäe wrote:

> On 15.03.2016 22:27, Jeff Johnson wrote:
>>         3) (recommended) rpm-5.4.16 uses db-6.1.23 (not 6.1.26) with
>>           DB_MULTIVERSION and DB_TXN_SNAPSHOT.
>>           DB_TXN_SNAPSHOT avoids deadlocks with copy-on-write rather than
>>           locking semantics.
> 
> so, if i use db-5.2, these changes be reverted in DB_CONFIG ?
> 
> 
> --- ../rpm-5.4.15/rpmdb/DB_CONFIG.in    2016-03-16 17:36:37.569145832 +0200
> +++ ../rpm-5.4.16/rpmdb/DB_CONFIG.in    2016-03-16 18:48:10.648775378 +0200
> @@ -1,10 +1,12 @@
> # ================ Environment
> -#add_data_dir .
> set_data_dir .
> -set_create_dir .
> set_lg_dir ./log
> set_tmp_dir ./tmp
> 
> +set_flags DB_MULTIVERSION on
> +set_flags DB_AUTO_COMMIT on
> +set_flags DB_TXN_SNAPSHOT on
> +
> 

Depends on whether db-5.2.x supports configuring those flags in DB_CONFIG.

(aside)
There are 3 different ways to configure BerkeleyDB
	1) hard-wired in C
	2) using /usr/lib/rpm/macros to pass in the appropriate info
	3) using DB_CONFIG which is the "official" (and documented) method to configure

I have done both 2) and 3) and there are almost no instances of hard-wired in rpm

Using DB_CONFIG to configure an rpmdb is the preferred approach because "ofiical" and documented.

Meanwhile try-and-see on db-5.2.x ... if you run into issues, holler and I'll figure a solution for you.

I'd suggest trying db-6.1.23 if you want exactly the same behavior as rpm-5.4.16 is being testesd with

73 de Jeff
> 
> -- 
> glen
> 
> _______________________________________________
> pld-devel-en mailing list
> pld-devel-en at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-devel-en