From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20628 invoked by uid 1002); 22 May 2003 21:31:57 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 11408 invoked from network); 22 May 2003 21:31:57 -0000 From: Grant Goodyear To: gentoo-dev@gentoo.org Cc: gentoo-core@gentoo.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-A7iXjsUAoMFaQEDp/os4" Organization: Message-Id: <1053639116.16598.14.camel@orange-pc.ces.clemson.edu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4- Date: 22 May 2003 17:31:57 -0400 Subject: [gentoo-dev] db4 X-Archives-Salt: 799673ad-c980-4b7b-927b-907579c3d302 X-Archives-Hash: 717299b9b8be7143d13c0cca8b8784c7 --=-A7iXjsUAoMFaQEDp/os4 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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.=20 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? -g2boojum- --=20 Grant Goodyear --=-A7iXjsUAoMFaQEDp/os4 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA+zUHMptxxUuD2W3YRAvkxAKCD1A99GtYcK01Y+Pci+IDJLHn7OACfZ5Gk dWOSWNwrY1ytsDJGwKkJ0DY= =1DFu -----END PGP SIGNATURE----- --=-A7iXjsUAoMFaQEDp/os4--