From owner-freebsd-ports@FreeBSD.ORG Sat Jan 28 21:44:51 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE11716A420 for ; Sat, 28 Jan 2006 21:44:51 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 761BB43D48 for ; Sat, 28 Jan 2006 21:44:50 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so838175nzo for ; Sat, 28 Jan 2006 13:44:50 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=mX53lVlgZqP8KWXbb+NQ7Y7sw/muDX0l3cp2YLVlMfXTEqIWEF2YB9m53iSFc3VdTx6WhDyP33/M8lHT9UYuxKIIA8WmnD/H95W2gf1dkdvSp7w+WPzVzIJvF5uIgTZiYi9TUjJgDkCMQ7I7a07w/yEUVz32E8yDYHAp0Y5kMYA= Received: by 10.37.2.70 with SMTP id e70mr3644168nzi; Sat, 28 Jan 2006 13:44:50 -0800 (PST) Received: by 10.37.20.67 with HTTP; Sat, 28 Jan 2006 13:44:50 -0800 (PST) Message-ID: Date: Sun, 29 Jan 2006 00:44:50 +0300 From: Andrew Pantyukhin To: Pav Lucistnik , Kris Kennaway , FreeBSD Ports MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: pkg_delete and modified files 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: Sat, 28 Jan 2006 21:44:52 -0000 Looking for a solution to the problem we stumbled upon, [which was keeping many modified files without the cmp trick described in the porter's handbook] I gave pkg_install/* sources a glance and now I'm thinking about a quick fix. The -f flag causes files to be deleted even in case of a checksum mismatch. In fact the -f flag is meant for something slightly else: Force removal of the package, even if a dependency is recorded or the deinstall or require script fails. So I'm thinking about another flag (like -F or a second -f) to control the behavior with modified files. I think that keeping them should be a default. I can't think of a thing that it will break, maybe you can. The cmp trick will still work. And it only takes a couple of lines to implement.