From owner-freebsd-ports Wed May 23 18:43: 3 2001 Delivered-To: freebsd-ports@freebsd.org Received: from casimir.physics.purdue.edu (casimir.physics.purdue.edu [128.210.146.111]) by hub.freebsd.org (Postfix) with ESMTP id AB9C437B423 for ; Wed, 23 May 2001 18:42:58 -0700 (PDT) (envelope-from will@physics.purdue.edu) Received: by casimir.physics.purdue.edu (Postfix, from userid 1000) id 34F8418A51; Wed, 23 May 2001 20:42:47 -0500 (EST) Date: Wed, 23 May 2001 20:42:47 -0500 From: Will Andrews To: The Hermit Hacker Cc: freebsd-ports@FreeBSD.ORG Subject: Re: Ports remembering old configurations ... Message-ID: <20010523204246.D19376@casimir.physics.purdue.edu> Reply-To: Will Andrews References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: ; from scrappy@hub.org on Wed, May 23, 2001 at 08:46:41PM -0300 X-Operating-System: Linux 2.2.18 sparc64 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, May 23, 2001 at 08:46:41PM -0300, The Hermit Hacker wrote: > Has anyone looked at what it would take to 'save' the configuration > between builds? Basically, if you build/install, it saves your build > options to a +CONFIG file or something like that ... when you go to build > it a second time (say to add a new option), it re-reads that file first > and sets the defaults based on that ... ? Yes, we've discussed this at length in the past. In fact I wrote a little paper on how to deal with this (and many other problems in ports) about eight months ago... -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message