From owner-freebsd-questions@FreeBSD.ORG Fri Oct 19 12:15:55 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD62216A417 for ; Fri, 19 Oct 2007 12:15:55 +0000 (UTC) (envelope-from fbsd06+PN=b113f054@mlists.homeunix.com) Received: from turtle-out.mxes.net (turtle-out.mxes.net [216.86.168.191]) by mx1.freebsd.org (Postfix) with ESMTP id 9E10913C43E for ; Fri, 19 Oct 2007 12:15:55 +0000 (UTC) (envelope-from fbsd06+PN=b113f054@mlists.homeunix.com) Received: from mxout-04.mxes.net (mxout-04.mxes.net [216.86.168.179]) by turtle-in.mxes.net (Postfix) with ESMTP id 405991640CF for ; Fri, 19 Oct 2007 07:58:12 -0400 (EDT) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 85B52D05A0 for ; Fri, 19 Oct 2007 07:58:10 -0400 (EDT) Date: Fri, 19 Oct 2007 12:58:06 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20071019125806.31a8b424@gumby.homeunix.com.> In-Reply-To: <18199.57951.791968.841899@jerusalem.litteratus.org> References: <471773D8.80503@mtmary.edu> <18199.32078.807531.40747@jerusalem.litteratus.org> <471786EC.3040803@mtmary.edu> <18199.57951.791968.841899@jerusalem.litteratus.org> X-Mailer: Claws Mail 3.0.0 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Updating Ports X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Oct 2007 12:15:55 -0000 On Thu, 18 Oct 2007 18:46:55 -0400 Robert Huff wrote: > 3) It is possible to put port-related settings in > /etc/make.conf. I discourage this, as that file gets used for > /every/ make session and I consider it asking for trouble to clutter > it with items that may accidentally overlap with another port. (The > risk is very small ... but it's still not the right tool for the > job.) People tend argue that the other way around, that putting port build settings in a configuration file that's specific to a single tool is wrong. You don't have to set anything globally in make.conf, you can do it like this: .if ${.CURDIR:M*/net-mgmt/net-snmp} WITH_TKMIB=yes .endif and that can be simplified by using portconf, which puts a single line in make.conf and reads in the settings from its own configuration file.