From owner-freebsd-current@FreeBSD.ORG Thu Jun 10 18:18:13 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC90C106564A; Thu, 10 Jun 2010 18:18:13 +0000 (UTC) (envelope-from julian@elischer.org) Received: from out-0.mx.aerioconnect.net (out-0-39.mx.aerioconnect.net [216.240.47.99]) by mx1.freebsd.org (Postfix) with ESMTP id AEED78FC08; Thu, 10 Jun 2010 18:18:13 +0000 (UTC) Received: from idiom.com (postfix@mx0.idiom.com [216.240.32.160]) by out-0.mx.aerioconnect.net (8.13.8/8.13.8) with ESMTP id o5AIIBFM013682; Thu, 10 Jun 2010 11:18:11 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id DAF442D6016; Thu, 10 Jun 2010 11:18:10 -0700 (PDT) Message-ID: <4C112C6C.50000@elischer.org> Date: Thu, 10 Jun 2010 11:18:20 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: John Baldwin References: <201006101346.59824.jhb@freebsd.org> In-Reply-To: <201006101346.59824.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on 216.240.47.51 Cc: current@freebsd.org Subject: Re: RFC: etcupdate tool in base? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jun 2010 18:18:13 -0000 On 6/10/10 10:46 AM, John Baldwin wrote: > I've had several folks ask me recently about importing etcupdate > (http://www.FreeBSD.org/~jhb/etcupdate) into the base system as an alternate > tool for updating /etc during upgrades. Do folks have any strong objections > to doing so? More details about how it works and an HTML version of the > manpage can be found at the URL above. > well mergemaster is in base so the options are: replace mergemaster, have both, move one to ports, or move both to ports. It does bring up the question (yet again) if we shouldn't have something that is between base and ports.. the keep base from bloating too much bit to still indicate that they are supported.