From owner-freebsd-questions@FreeBSD.ORG Fri Oct 19 13:22:11 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 943ED16A421 for ; Fri, 19 Oct 2007 13:22:11 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 540F313C481 for ; Fri, 19 Oct 2007 13:22:11 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from mr02.lnh.mail.rcn.net ([207.172.157.22]) by smtp02.lnh.mail.rcn.net with ESMTP; 19 Oct 2007 09:22:10 -0400 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr02.lnh.mail.rcn.net (MOS 3.8.3-GA) with ESMTP id NXM79351; Fri, 19 Oct 2007 09:22:10 -0400 (EDT) Received: from 209-6-22-188.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.22.188]) by smtp01.lnh.mail.rcn.net with ESMTP; 19 Oct 2007 09:24:36 -0400 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18200.44923.816309.975738@jerusalem.litteratus.org> Date: Fri, 19 Oct 2007 09:22:03 -0400 To: freebsd-questions@freebsd.org In-Reply-To: <20071019125806.31a8b424@gumby.homeunix.com.> References: <471773D8.80503@mtmary.edu> <18199.32078.807531.40747@jerusalem.litteratus.org> <471786EC.3040803@mtmary.edu> <18199.57951.791968.841899@jerusalem.litteratus.org> <20071019125806.31a8b424@gumby.homeunix.com.> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr02.lnh.mail.rcn.net) 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 13:22:11 -0000 RW writes: > > 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. And I agree in part. On the other hand, how many use multiple configuration tools? If there were something that applied to _every_ port - say a compiler flag - I'd probably be OK with putting it in make.conf. > 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 That looks good. > 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. This as well, though I see it as reducing (in practice) to my solution. Robert Huff