From owner-freebsd-ports@FreeBSD.ORG Sat Jul 9 03:45:41 2005 Return-Path: X-Original-To: ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3411916A41C for ; Sat, 9 Jul 2005 03:45:41 +0000 (GMT) (envelope-from ade@FreeBSD.org) Received: from mail.lovett.com (foo.lovett.com [67.134.38.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6C6843D46 for ; Sat, 9 Jul 2005 03:45:40 +0000 (GMT) (envelope-from ade@FreeBSD.org) Received: from hellfire.lovett.com ([67.134.38.149]:59915) by mail.lovett.com with esmtpa (Exim 4.51 (FreeBSD)) id 1Dr6Hc-000KT2-1b; Fri, 08 Jul 2005 20:45:40 -0700 Message-ID: <42CF4853.701@FreeBSD.org> Date: Fri, 08 Jul 2005 20:45:23 -0700 From: Ade Lovett User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ben Gross References: In-Reply-To: X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: ade@lovett.com Cc: ports@FreeBSD.org Subject: Re: spamprobe and Berkeley DB X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jul 2005 03:45:41 -0000 Ben Gross wrote: > First, thanks for keep the port up to date. Overall, the spamprobe port > works well. The only issue for me is it has an old berkeley DB port, > db4 hard coded which is less reliable than the newer Berkeley DB ports. > If the Berkeley DB selection code could be ripped from another port > such as www/apache2, security/cyrus-sasl2 or mail/ postfix and put in > the spamprobe port it would make it much easier to use db42 or even db43. A more logical approach would be to develop appropriate code for USE_BDB/USE_BDB_VER/WANT_BDB = (3,4,41,42, maybe even 185 for base system), and implement that in bsd.port.mk, in a similar manner to the MYSQL and PGSQL knobs. It could even warrant a separate bsd.database.mk file where such things are kept, working towards having bsd.port.mk only contain the heavy-lifting infrastructural work for the ports system as a whole. Once the BDB knobs are implemented, it should be relatively straightforward to sweep the tree and fix up all ports to use the same system for Berkeley DB usage, rather than the myriad of different ways in use now. Fancy writing some make(1) code? :) -aDe