From owner-freebsd-ports@FreeBSD.ORG Wed Jul 13 10:04:33 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 0ED5216A41C for ; Wed, 13 Jul 2005 10:04:33 +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 CED0C43D46 for ; Wed, 13 Jul 2005 10:04:32 +0000 (GMT) (envelope-from ade@FreeBSD.org) Received: from hellfire.lovett.com ([67.134.38.149]:53511) by mail.lovett.com with esmtpa (Exim 4.51 (FreeBSD)) id 1Dse6R-000JKY-GB; Wed, 13 Jul 2005 03:04:31 -0700 Message-ID: <42D4E738.8040101@FreeBSD.org> Date: Wed, 13 Jul 2005 03:04:40 -0700 From: Ade Lovett User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vsevolod Stakhov References: <42CF4853.701@FreeBSD.org> <42D4D46B.7080100@highsecure.ru> In-Reply-To: <42D4D46B.7080100@highsecure.ru> X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: freebsd@lovett.com Cc: ports@FreeBSD.org, Ben Gross 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: Wed, 13 Jul 2005 10:04:33 -0000 Vsevolod Stakhov wrote: > I've already make this (so called bsd.bdb.mk). Should I send PR about it? If you rename it to bsd.database.mk, and extend it such that all the existing PGSQL and MYSQL knobs from bsd.port.mk are included, absolutely -- that part should be a simple cut-and-paste operation (don't forget the necessary patches to bsd.port.mk itself to remove any functionality that is now in bsd.database.mk) Test a before-and-after with 'make index' and verify that they're the same, then submit the PR, let me know the number, and I'll make sure it gets in the hands of portmgr@ for an -exp build cluster run. Once that's done, the changes can be committed (assuming no issues), and then bsd.database.mk can be worked on in (relative) isolation from the rest of the tree -- I'm certainly willing to co-ordinate this work with other committers and port maintainers. -aDe