From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev-return-3290-arch-gentoo-dev=gentoo.org@gentoo.org>
Received: (qmail 3509 invoked by uid 1002); 23 May 2003 07:59:13 -0000
Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:gentoo-dev@gentoo.org>
List-Help: <mailto:gentoo-dev-help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev-unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-dev-subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@gentoo.org
Received: (qmail 16556 invoked from network); 23 May 2003 07:59:13 -0000
From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@gentoo.org
Date: Fri, 23 May 2003 09:59:03 +0200
User-Agent: KMail/1.5.2
References: <1053639116.16598.14.camel@orange-pc.ces.clemson.edu>
In-Reply-To: <1053639116.16598.14.camel@orange-pc.ces.clemson.edu>
MIME-Version: 1.0
Content-Type: multipart/signed;
  protocol="application/pgp-signature";
  micalg=pgp-sha1;
  boundary="Boundary-02=_PTdz+EFQE40Knio";
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200305230959.11301.pauldv@gentoo.org>
Subject: Re: [gentoo-dev] db4
X-Archives-Salt: d17ddf01-4d39-48f1-8578-15bdb56a0dd0
X-Archives-Hash: 0f054dca3bd1d1284672d206b8234d2b

--Boundary-02=_PTdz+EFQE40Knio
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Thursday 22 May 2003 23:31, Grant Goodyear wrote:
> After the 1.4 release, I think it would be a good idea to make another
> pass at making db4 the default in gentoo.  We're starting to get
> packages such as the latest openldap that require db4.  The current
> problem is that not all packages will build w/ db4 right now, but
> emerging db4 will stomp some files from db1 and db3 (and vice versa),
> from what I've seen.  We could employ slots and a set of /usr/lib/dbx
> directories, but that's fairly intrusive.  Most packages do now build w/
> db4 quite well, as it emulates db1 and db3 fairly nicely, or they can be
> patched to do so, and I think that's the better long-term solution.
> Unfortunately, some packages still refuse to behave.  One example is
> courier-imap, which currently requires either db3 or gdbm.  Debian's
> solution for their db4-based unstable tree has been to just compile
> courier-imap w/ gdbm.  Presumably, if we want to give users a choice
> about the backend we could build db4 support in statically, but I don't
> have a feeling for how much of a pain that would be.
>
> Thoughts?

Basically the binaries are bitten by this. I was thinking we could just ren=
ame=20
them from db_archive to db4_archive  (where archive is just an example)

Paul

=2D-=20
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.cs.kun.nl/~pauldv

--Boundary-02=_PTdz+EFQE40Knio
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA+zdTPbKx5DBjWFdsRAj9mAJ9olHhkvoViITypNEOqepZ9qpuLugCeN53j
ZWXI4CRtIANK3YMo+3Sjn78=
=ma1d
-----END PGP SIGNATURE-----

--Boundary-02=_PTdz+EFQE40Knio--