From owner-freebsd-ports@FreeBSD.ORG Wed Jan 2 20:47:17 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AD555728 for ; Wed, 2 Jan 2013 20:47:17 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 727E825E for ; Wed, 2 Jan 2013 20:47:17 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id B850728429 for ; Wed, 2 Jan 2013 21:37:09 +0100 (CET) Received: from [192.168.1.2] (unknown [89.177.49.69]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id D59B528428 for ; Wed, 2 Jan 2013 21:37:08 +0100 (CET) Message-ID: <50E49A73.2070008@quip.cz> Date: Wed, 02 Jan 2013 21:37:07 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: What is policy about auto-editing config files on port install / deinstall? Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jan 2013 20:47:17 -0000 Is somewhere written policy or portmgr recommendation about ports behavior on install / deinstall? I am talking about some ports doing "nasty" things. Some ports are stopping services on deinstall, some not. Some ports are editing "my config files" on deinstall, so even on upgrade procedure I must check if port did some changes before I can restart target daemon. For example some Apache modules (mod_bw, mod_xsendfile...) are commenting out load_module lines in httpd.conf so I got syntax error on Apache restart after upgrade of mentioned module and Apache failed to start. These inconsistencies are really boring. I know it is made by AP_GENPLIST, but not all modules are using it and I think it is really bad idea to touch user's config files this way. I prefere not to change my files in any way (on install and on deinstall), just print message "what should user do". Because this auto-editing is doing more problems than benefits on each upgrade. Miroslav Lachman