From owner-freebsd-ports@FreeBSD.ORG Tue Jun 18 15:59:41 2013 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A761D5E4 for ; Tue, 18 Jun 2013 15:59:41 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) by mx1.freebsd.org (Postfix) with ESMTP id 56871131F for ; Tue, 18 Jun 2013 15:59:40 +0000 (UTC) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.69) (envelope-from ) id 1UoyJl-0003wX-71 for ports@freebsd.org; Tue, 18 Jun 2013 22:59:37 +0700 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id r5IG0gEd030449 for ; Tue, 18 Jun 2013 23:00:42 +0700 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id r5IG0bxI030437 for ports@freebsd.org; Tue, 18 Jun 2013 23:00:37 +0700 (NOVT) (envelope-from danfe) Date: Tue, 18 Jun 2013 23:00:37 +0700 From: Alexey Dokuchaev To: ports@freebsd.org Subject: Proposal: further OptionsNG improvements Message-ID: <20130618160037.GA26677@regency.nsu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 15:59:41 -0000 Hi there, Now as I understand old-skool OPTIONS knob support is removed, can we do something about ugliness of newish OPTIONS_DEFINE[_arch]/OPTIONS_DEFAULT [_arch] pair of knobs? I am thinking about the following syntax (using now free-again OPTIONS knob, instead of several OPTIONS_DEFINE/OPTIONS_DEFAULT definitions): OPTIONS= FOO:on BAR ASM/i386,amd64:on,powerpc ... Ditto for OPTIONS_RADIO et al. This will also be kind of reminiscent to existing USE_AUTOCONF and recently added USES knob. It can get a bit hard to parse for architecture-specific options, but they appear relatively rare, yet for most cases new syntax seems cleaner to me. What do people think? I'd like to gather some opinions before trying to sit down and write a patch (unless someone(tm) beats me on it). ./danfe