From owner-freebsd-ports@FreeBSD.ORG Sun Jun 10 21:27:46 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 769B2106566B for ; Sun, 10 Jun 2012 21:27:46 +0000 (UTC) (envelope-from adams-freebsd@ateamsystems.com) Received: from fss.sandiego.ateamservers.com (fss.sandiego.ateamservers.com [69.55.229.149]) by mx1.freebsd.org (Postfix) with ESMTP id 5AEB58FC0A for ; Sun, 10 Jun 2012 21:27:46 +0000 (UTC) Received: from [192.168.15.220] (unknown [118.175.84.92]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by fss.sandiego.ateamservers.com (Postfix) with ESMTPSA id E43C8B9F24 for ; Sun, 10 Jun 2012 17:27:44 -0400 (EDT) Message-ID: <4FD51147.3040004@ateamsystems.com> Date: Mon, 11 Jun 2012 04:27:35 +0700 From: Adam Strohl User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4FD50115.1070904@ateamsystems.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Retro-actively adjust port's deinstall operations? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jun 2012 21:27:46 -0000 On 6/11/2012 3:38, Chris Rees wrote: > Actually if the older version doesn't install a .sample file (as it > doesn't), you could put a big warning in for it: > > .include > > .if exists(${PREFIX}/whateverconfigfile)&& > !exists(${PREFIX}/whateverconfigfile.sample) > IGNORE= Please see UPDATING note {date} > .endif Where/when would this trigger? > > Stick a note in UPDATING (perhaps like 20110815), and send a HEADSUP to ports@: > > BEFORE you deinstall couchdb, make sure you take a backup of > default.ini, because the port will clobber it. I'm assuming this was a typo but just in case: Its the local.ini file that is the issue (and contains the overrides against default.ini as well as the admin account usernames and password hashes). > > I've grabbed your PR and will investigate tomorrow. Cool, thanks! -- Adam Strohl http://www.ateamsystems.com/