From owner-freebsd-ports@FreeBSD.ORG Sun Jun 10 20:18:40 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 F16D21065676 for ; Sun, 10 Jun 2012 20:18:40 +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 D03198FC12 for ; Sun, 10 Jun 2012 20:18:40 +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 1F0F7B9F23 for ; Sun, 10 Jun 2012 16:18:38 -0400 (EDT) Message-ID: <4FD50115.1070904@ateamsystems.com> Date: Mon, 11 Jun 2012 03:18:29 +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 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 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 20:18:41 -0000 Hello, I've just submitted a PR to update the CouchDB port from 1.1.0 to 1.2.0: http://www.freebsd.org/cgi/query-pr.cgi?pr=168923 Background: CouchDB's local.ini file stores all overridden options and default.ini the defaults, similar to /etc/rc.conf & /etc/defaults/rc.conf. While updating the port I discovered that the existing port lists local.ini directly in pkg-plist instead of installing a local.ini.sample file and doing proper comparisons/tests for changes. So it blindly removes this file on deinstall. If my diff in the above PR is accepted when people uninstall the existing 1.1.0 port it will remove their config file. The new port will see that there is no local.ini and copy in the sample for them but this is really awful for obvious reasons. Is there a way to reach people with a warning about this _before_ they uninstall/reinstall so they can back up the file before upgrading? Or is /usr/ports/UPDATING it? (and do I need to do anything special to have this listed there?) P.S. Any other feedback on the PR/diff is welcome. -- Adam Strohl http://www.ateamsystems.com/