From owner-freebsd-ports@FreeBSD.ORG Sun Nov 16 12:22:40 2003 Return-Path: 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 4AE8216A4CE for ; Sun, 16 Nov 2003 12:22:40 -0800 (PST) Received: from mailout.informatik.tu-muenchen.de (mailout.informatik.tu-muenchen.de [131.159.0.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AC3843FDD for ; Sun, 16 Nov 2003 12:22:37 -0800 (PST) (envelope-from barner@in.tum.de) Received: from zi025.glhnet.mhn.de (localhost.glhnet.mhn.de. [127.0.0.1]) by zi025.glhnet.mhn.de (8.12.9p2/8.12.9) with ESMTP id hAGKMBmR071854; Sun, 16 Nov 2003 21:22:11 +0100 (CET) (envelope-from simon@zi025.glhnet.mhn.de) Received: (from simon@localhost) by zi025.glhnet.mhn.de (8.12.9p2/8.12.9/Submit) id hAGKMAHS071853; Sun, 16 Nov 2003 21:22:10 +0100 (CET) (envelope-from simon) Date: Sun, 16 Nov 2003 21:22:10 +0100 From: Simon Barner To: Richard Coleman Message-ID: <20031116202210.GI556@zi025.glhnet.mhn.de> References: <3FB7B686.5080904@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FB7B686.5080904@mindspring.com> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at informatik.tu-muenchen.de cc: freebsd-ports@freebsd.org Subject: Re: listing the WITH_* variables for each package X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Nov 2003 20:22:40 -0000 > One thing I always find annoying is the necessity to dig through the > Makefiles to look at all the WITH_* variables that are available when > compiling a port. I think there are a couple easy options to do > something better here. > > 1. Have a suggestion in the porter's handbook to list them in pkg-descr. > Along with each WITH variable would be a one line description. This > would be very helpful and not much extra work. > > 2. Create another (optional) file such as pkg-options in each port. It > would simply be a listing of the available WITH options and a one line > description. Experimental or developer-only options could be left out > or marked differently. This would also open additional automated build > possibilities such as doing test builds with all possible subsets of the > WITH variables (obviously this would be time consuming, but wouldn't > need to be done very often). 3. A `make options' target similar to `make maintainer'