From owner-freebsd-ports-bugs@FreeBSD.ORG Sun Oct 16 17:40:16 2005 Return-Path: X-Original-To: freebsd-ports-bugs@hub.freebsd.org Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31A2416A41F for ; Sun, 16 Oct 2005 17:40:16 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFD7443D49 for ; Sun, 16 Oct 2005 17:40:15 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j9GHeF8d074086 for ; Sun, 16 Oct 2005 17:40:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j9GHeF7h074085; Sun, 16 Oct 2005 17:40:15 GMT (envelope-from gnats) Date: Sun, 16 Oct 2005 17:40:15 GMT Message-Id: <200510161740.j9GHeF7h074085@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: "Michael C. Shultz" Cc: Subject: Re: ports/87497: [NON-MAINTAINER] sysutils/portmanager update to 0.3.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Michael C. Shultz" List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2005 17:40:16 -0000 The following reply was made to PR ports/87497; it has been noted by GNATS. From: "Michael C. Shultz" To: Volker Stolz , bug-followup@freebsd.org Cc: Subject: Re: ports/87497: [NON-MAINTAINER] sysutils/portmanager update to 0.3.0 Date: Sun, 16 Oct 2005 10:35:47 -0700 On Sunday 16 October 2005 10:01, you wrote: > Am 16. Oct 2005 um 17:54 CEST schrieb Michael C. Shultz: > > On Sunday 16 October 2005 06:56, you wrote: > > > How about using OPTIONS instead of pre-fetch? > > > > > > Volker > > > > I don't care for OPTIONS, there are much better ways > > to handle WITH_* variables, read man (1) portmanager > > for a few suggestions. > > OPTIONS is the only way of providing meta-data that a port has > any options at all. Personally I do this: cat Makefile: grep WITH > Quoting the Porter's Handbook: "...the ports system provides hooks that > the port author can use to control which configuration should be built. > Supporting these properly will make users happy..." > > Volker I think you may be missing the context, in your example is'nt the author refering to proper use of "WITH_*" and "WITHOUT_* variables? The author then seems to recommend OPTIONS as a way to manage these variables, I have no problem with that recommendation, its just I choose to manage WITH_*, and WITHOUT_* in a different manner that works better with portmanager. ref: 5.11 Makefile Options Some large applications can be built in a number of configurations, adding functionality if one of a number of libraries or applications is available. Examples include choice of natural (human) language, GUI versus command-line, or type of database to support. Since not all users want those libraries or applications, the ports system provides hooks that the port author can use to control which configuration should be built. Supporting these properly will make users happy, and effectively provide 2 or more ports for the price of one. 5.11.1 WITH_* and WITHOUT_* These variables are designed to be set by the system administrator. There are many that are standardized in ports/Mk/bsd.*.mk; others are not, which can be confusing. If you need to add such a configuration variable, please consider using one of the ones from the following list. Note: You should not assume that a WITH_* necessarily has a corresponding WITHOUT_* variable and vice versa. In general, the default is simply assumed. Note: Unless otherwise specified, these variables are only tested for being set or not set, rather than being set to some kind of variable such as YES or NO.