From owner-freebsd-current@FreeBSD.ORG  Sat Jan 14 21:03:03 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35])
	by hub.freebsd.org (Postfix) with ESMTP id 508AC1065678
	for <freebsd-current@FreeBSD.org>; Sat, 14 Jan 2012 21:03:03 +0000 (UTC)
	(envelope-from dougb@FreeBSD.org)
Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org
	[IPv6:2001:4f8:fff6::36])
	by mx2.freebsd.org (Postfix) with ESMTP id 8C25114F994;
	Sat, 14 Jan 2012 21:03:02 +0000 (UTC)
Message-ID: <4F11ED85.5050202@FreeBSD.org>
Date: Sat, 14 Jan 2012 13:03:01 -0800
From: Doug Barton <dougb@FreeBSD.org>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:9.0) Gecko/20111222 Thunderbird/9.0
MIME-Version: 1.0
To: Jilles Tjoelker <jilles@stack.nl>
References: <4F114577.30201@FreeBSD.org> <20120114144445.GA53777@stack.nl>
In-Reply-To: <20120114144445.GA53777@stack.nl>
X-Enigmail-Version: undefined
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-current <freebsd-current@FreeBSD.org>
Subject: Re: HEADS UP: set_rcvar() removed from rc.subr
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jan 2012 21:03:03 -0000

On 01/14/2012 06:44, Jilles Tjoelker wrote:
> Why must the 2-argument form of set_rcvar die at the same time? It is
> used very differently and does not cause unnecessary forks. Instead, it
> is called in the same shell environment to define additional rc.conf
> variables that have defaults and are shown in '<script> rcvar'.

Because it can just as easily be accomplished the same way that all the
other rcvar-related things are:

rcvar=foo_enable
: ${foo_enable:=NO}

And before you spend too much time bemoaning its demise, quick question
... how many places was it used?


Doug

-- 

	You can observe a lot just by watching.	-- Yogi Berra

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/