From owner-freebsd-ports@FreeBSD.ORG Fri Jan 14 21:12:11 2005 Return-Path: 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 923F116A4CE for ; Fri, 14 Jan 2005 21:12:11 +0000 (GMT) Received: from mail2out.barnet.com.au (mail2out.barnet.com.au [202.83.176.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id B06BC43D3F for ; Fri, 14 Jan 2005 21:12:10 +0000 (GMT) (envelope-from edwin@mavetju.org) Received: by mail2out.barnet.com.au (Postfix, from userid 27) id 04F1B707445; Sat, 15 Jan 2005 08:12:09 +1100 (EST) X-Viruscan-Id: <41E835A800012ECCB73F05@BarNet> Received: from mail2-auth.barnet.com.au (mail2.barnet.com.au [202.83.176.13]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) Authority" (verified OK)) by mail2.barnet.com.au (Postfix) with ESMTP id B26EF707444; Sat, 15 Jan 2005 08:12:08 +1100 (EST) Received: from k7.mavetju (edwin-3.int.barnet.com.au [10.10.12.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) Certificate Authority" (verified OK)) by mail2-auth.barnet.com.au (Postfix) with ESMTP id 1CFAD707439; Sat, 15 Jan 2005 08:12:08 +1100 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id 096E36139; Sat, 15 Jan 2005 08:12:07 +1100 (EST) Date: Sat, 15 Jan 2005 08:12:06 +1100 From: Edwin Groothuis To: Kirill Ponomarew Message-ID: <20050114211206.GF1175@k7.mavetju> References: <20050113062739.GA28658@xor.obsecurity.org> <20050113180504.GA26064@xor.obsecurity.org> <20050114130404.250d6e26@apircalabu.dsd.ro> <20050114112918.GF69532@voodoo.oberon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050114112918.GF69532@voodoo.oberon.net> User-Agent: Mutt/1.5.6i cc: freebsd-ports@freebsd.org Subject: Re: HEADS UP: pkg-plist strict enforcement starting X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 21:12:11 -0000 On Fri, Jan 14, 2005 at 12:29:18PM +0100, Kirill Ponomarew wrote: > On Fri, Jan 14, 2005 at 01:04:04PM +0200, Adi Pircalabu wrote: > > > I'm going to be careful about not allowing the "questionable" packages > > > to fall foul of the pkg-plist checking, until we decide one way or the > > > other whether they should be considered "broken". > > > > This is a tricky situation from my point of view. I'm following this > > thread with a lot of interest since I'll be managing a port which CAN > > NOT honor pkg-plist strict checking. Here are few details: > > > > - The configuration files are created and heavily modified at install > > time from .dist files, will be modified as needed and should not be > > deleted at uninstall - the configuration should be kept for a later > > upgrade. This will definitely break "make install deinstall" on the > > packages cluster, but the files are required since they must contain > > information about various modules and plugins of the port, and this > > information must be written through a daemon started at post-install. > > You can try cmp(1) in pkg-plist to compare configurations files. > Take a look at ports collection, there are enough examples. Maybe we need two additional @ commands for pkg-plist: - @dirrmifempty foo/bar does do what "@unexec rmdir %D/foo/bar 2>/dev/null || true" does. - @rmifdifferent foo/bar foo/baz does do what "@unexec cmp %D/foo/bar %D/foo/baz && rm %D/foo/bar" does. This way we - have an easy and consistent syntax for a difficult command - have less chance for errors (forgetting %D, && instead of ||) Comments? Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://weblog.barnet.com.au/edwin/