From owner-freebsd-ports@FreeBSD.ORG Tue Jan 21 09:36:41 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 61E885DA for ; Tue, 21 Jan 2014 09:36:41 +0000 (UTC) Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DBED81868 for ; Tue, 21 Jan 2014 09:36:40 +0000 (UTC) Received: by mail-la0-f50.google.com with SMTP id ec20so6471409lab.9 for ; Tue, 21 Jan 2014 01:36:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=GHTmbOvKF/9B6sHyQuofjDvv0RQVQVeiA6wzs6QM7To=; b=DPQYmdzCgEFYvp6TxXoL5LVU4AxQHXSZtR6IldOeJ8vaLF541VXIaPPhOU+SCfm4e5 f5hEPC/aCHxWl+bFf5LjpawUV6if0/ZCWmjitrvEF6eFn+U1W+X603t0ERMbE6zxoCZm twm0hAraD6W/AS4uOtsXMkXm4sbfYYbbFSJ8Pnu8DET8YVD6XiFHccRPdUUPol6s1VqB FU77ERsNYM77IcTPzS8z8A7+9FbamLCbN+hFSIDYuMDNPv32d3/G++BFCrsExQXgcS6S JbziqolxNnlKYRA8OGTovYUKyhYetI8orMsgyVyI+Fqhll0KBrQvR0qdUMzUMch9lpYI WH2w== X-Received: by 10.112.164.5 with SMTP id ym5mr486406lbb.48.1390296998965; Tue, 21 Jan 2014 01:36:38 -0800 (PST) Received: from [192.168.1.129] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPSA id m3sm3512275lbp.13.2014.01.21.01.36.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Jan 2014 01:36:38 -0800 (PST) Message-ID: <52DE3FA5.6040407@gmail.com> Date: Tue, 21 Jan 2014 11:36:37 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Matthew Pounsett , freebsd-ports@freebsd.org Subject: Re: per-port make.conf options and hyphenated port names References: <92E0B243-3705-437A-80C8-DB9AAF938A3D@conundrum.com> In-Reply-To: <92E0B243-3705-437A-80C8-DB9AAF938A3D@conundrum.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 09:36:41 -0000 21.01.2014 03:01, Matthew Pounsett wrote: > > At some point in the last couple of weeks I was pointed at as what has been implemented to deprecate make.conf settings such as “WITHOUT_X11=yes”. That document says it has been committed, but the porters handbook section on OPTIONS doesn’t discuss the ${port}_SET/${port}_UNSET syntax, and I can’t find mention of it in /usr/ports/KNOBS either. > > I’m trying to find specifics on the implementation because I’ve run into a case that document doesn’t seem to plan for: trying to set per-port options for a hyphenated port name. > > Specifically, I’m trying to do this: > virtualbox-ose-additions_UNSET=X11 > > Hyphenated variable names don’t work in most shells. I think some older versions of csh could set them, but couldn't reference them, and tinderbox’s sh scripts blow right up when they encounter that. > > Digging through /usr/ports/Mk/ I can’t find anywhere that $UNIQUENAME is modified to guarantee that it references a safe variable name (i.e. I don’t see anywhere that $UNIQUENAME has reserved characters removed from it before use). So, given that a lot of times $UNIQUENAME is just the name of the port, and a lot of ports have hyphens in their names, how is this meant to be dealt with? > > Thanks for any pointers or help! Excuse me hijacking the thread but doesn't ports-mgmt/portconf do almost the same? -- Sphinx of black quartz, judge my vow.