head 1.2;
access;
symbols
RPM_4_2_1:1.1.1.5
RPM_4_2:1.1.1.5
RPM_4_1_1:1.1.1.5
RPM_4_1:1.1.1.4
RPM_4_0_5:1.1.1.3
RPM_4_0_4:1.1.1.2
RPM_4_0_3:1.1.1.1
RPM:1.1.1;
locks; strict;
comment @# @;
1.2
date 2008.01.02.09.55.55; author rse; state dead;
branches;
next 1.1;
commitid z4cpSiAhOCXk5PLs;
1.1
date 2001.07.23.20.45.38; author rse; state Exp;
branches
1.1.1.1;
next ;
1.1.1.1
date 2001.07.23.20.45.38; author rse; state Exp;
branches;
next 1.1.1.2;
1.1.1.2
date 2002.01.08.00.30.12; author rse; state Exp;
branches;
next 1.1.1.3;
1.1.1.3
date 2003.01.18.13.49.04; author rse; state Exp;
branches;
next 1.1.1.4;
1.1.1.4
date 2001.05.13.19.58.47; author rse; state Exp;
branches;
next 1.1.1.5;
1.1.1.5
date 2003.01.18.14.05.00; author rse; state Exp;
branches;
next ;
desc
@@
1.2
log
@remove the ancient RPM 4.2.1 source tree copy
@
text
@
Berkeley DB Reference Guide: Release 2.0: upgrade requirements
- Berkeley DB Reference Guide:
- Upgrading Berkeley DB Applications
|
  
|
Release 2.0: upgrade requirements
You will need to upgrade your on-disk databases, as all access method
database formats changed in the Berkeley DB 2.0 release. For information on
converting databases from Berkeley DB 1.85 to Berkeley DB 2.0, see the
db_dump185 and db_load documentation. As database
environments did not exist prior to the 2.0 release, there is no
question of upgrading existing database environments.
Copyright Sleepycat Software
@
1.1
log
@Initial revision
@
text
@d1 1
a1 1
@
1.1.1.1
log
@Import: RPM 4.0.3
@
text
@@
1.1.1.2
log
@Import: RPM 4.0.4
@
text
@d1 1
a1 1
@
1.1.1.3
log
@Import: RPM 4.0.5
@
text
@d2 1
a2 1
a3 1
@
1.1.1.4
log
@Import: RPM 4.1
@
text
@d2 1
a2 1
d4 1
@
1.1.1.5
log
@Import: RPM 4.1.1
@
text
@d2 1
a2 1
a3 1
@