From owner-freebsd-questions@FreeBSD.ORG Sat Jul 28 21:57:30 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 D27FE16A417 for ; Sat, 28 Jul 2007 21:57:30 +0000 (UTC) (envelope-from njm@njm.f2s.com) Received: from outmail1.freedom2surf.net (outmail1.freedom2surf.net [194.106.33.237]) by mx1.freebsd.org (Postfix) with ESMTP id 7B3F213C428 for ; Sat, 28 Jul 2007 21:57:30 +0000 (UTC) (envelope-from njm@njm.f2s.com) Received: from oberon.njm.f2s.com (i-195-137-21-170.freedom2surf.net [195.137.21.170]) by outmail1.freedom2surf.net (Postfix) with ESMTP id A77AC50CE5; Sat, 28 Jul 2007 22:37:51 +0100 (BST) Received: from oberon.njm.f2s.com (localhost.njm.f2s.com [127.0.0.1]) by oberon.njm.f2s.com (8.14.1/8.14.1) with ESMTP id l6SLbpiX093271; Sat, 28 Jul 2007 22:37:51 +0100 (BST) (envelope-from njm@oberon.njm.f2s.com) Received: (from njm@localhost) by oberon.njm.f2s.com (8.14.1/8.14.1/Submit) id l6SLboB2093270; Sat, 28 Jul 2007 22:37:50 +0100 (BST) (envelope-from njm) Date: Sat, 28 Jul 2007 22:37:50 +0100 From: "N.J. Mann" To: CyberLeo Kitsana Message-ID: <20070728213750.GA93017@oberon.njm.f2s.com> Mail-Followup-To: CyberLeo Kitsana , FreeBSD Questions References: <46AB9EB4.5080305@cyberleo.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46AB9EB4.5080305@cyberleo.net> X-Operating-System: FreeBSD 6.2-STABLE User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD Questions Subject: Re: Custom builds from 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: Sat, 28 Jul 2007 21:57:30 -0000 In message <46AB9EB4.5080305@cyberleo.net>, CyberLeo Kitsana wrote: > > My question concerns building ports with custom options. > > With some ports, 'make config' governs the options, and stores them in a > file someplace so they are honored the next time you build or upgrade > the port. > > With most ports, however, this is controlled by passing variables on the > command line or via the environment. > > The most obvious location for these variables to be placed, so that they > may affect recursive builds and upgrades, is make.conf. However, I've > noticed that some ports use the same variable names for similar options > ('WITH_MYSQL'), when I may not want that option set in both ports. > > Is there a way to specify which ports certain options are to be applied > to, without having to craft custom command lines and build ports > individually? Is ports-mgmt/portconf what you are looking for? Cheers, Nick. --