[ZODB-Dev] Using BerkeleyDB

[Barry Warsaw]

On Thu, 2003-08-14 at 06:49, Harald Koschinski wrote:

> Sorry asking again - I don't want to waste your time - but there is no
> ZODB3-3_1-branch

I'm not sure what you're using to get the list of tags, but here's what
I'm doing.  cd to the top of your ZODB3 checkout and do:

% cvs log README.txt | less

RCS file: /cvs-repository/ZODB3/README.txt,v
Working file: README.txt
head: 1.19
branch:
locks: strict
access list:
symbolic names:
        ZODB3-3_1-boston-branch: 1.7.4.13.0.2
        ZODB3-3-3-a1: 1.19.4.1
        ZODB-3-1-2-final: 1.7.4.13
        zodb33-devel-branch: 1.19.0.4
        ZODB3-3_1-20030625: 1.7.4.12
        ZODB3-3-2b2: 1.19
        ZODB3-3_2-branch: 1.19.0.2
        ZODB3-3-1-2-b2: 1.7.4.12
        jeremy-more-mysteries-branch: 1.7.4.11.0.4
        tim-loading_oids_status-branch: 1.7.4.11.0.2
        bonzai-zeo_ainval-snap_20030607: 1.7.4.11
        ZODB3-3-2b1: 1.18
        pre-auth-merge: 1.14
        Release_20030527: 1.7.4.11
        ZODB3-3-1-2-b1: 1.7.4.11
        ZODB3-auth-branch: 1.14.0.2
        ZODB3-3-1-1-final: 1.7.4.9
        ZODB3-3-1-1b2: 1.7.4.8
        VTS3-branch: 1.7.4.6.0.4
        ZODB3-3-2a1: 1.14
        VTS3-fork: 1.7.4.6
        zconfig-schema-devel-branch: 1.12.0.2
        ZODB3-fast-restart-merge-from-1: 1.7.4.6
        ZODB3-fast-restart-merge-to-1: 1.7.4.6
        ZODB3-fast-restart-fork: 1.7.4.6
        ZODB3-fast-restart-branch: 1.7.4.6.0.2
        ZODB3-4-sync: 1.12
        ZODB3-3-1-1b1: 1.7.4.5
        ZODB3-3-1-1-beta-0: 1.7.4.5
        ZODB3-3-1-restore-fixed: 1.7.4.5
        ZODB3-restore-debug-branch: 1.7.4.5.0.4
        ZODB3-pre-deadlock-merge: 1.7.4.5
        ZOD3-deadlock-merge: 1.7.4.5
        deadlock-fix-11_01: 1.7.4.5
        ZODB3-deadlock-debug-branch: 1.7.4.5.0.2
        ZODB3-3-1-final: 1.7.4.5
        ZODB3-3-1b3: 1.7.4.4
        ZODB3-3-1b2: 1.7.4.2
        ZODB3-3-1b1: 1.6
        ZODB3-3_1-branch: 1.7.0.4
-------^^^^^^^^^^^^^^^^^^^^^^^^^

Whoop, there it is. :)

Remember that this is a branch tag.  The latest and greatest merged
Berkeley code is on the head of that branch so it hasn't been released
yet and there is no non-branch tag that points to it yet.

-Barry