From owner-freebsd-ports@FreeBSD.ORG Fri Jan 14 11:29:45 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 035D216A4CE for ; Fri, 14 Jan 2005 11:29:45 +0000 (GMT) Received: from voodoo.oberon.net (voodoo.oberon.net [212.118.165.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6A5943D58 for ; Fri, 14 Jan 2005 11:29:44 +0000 (GMT) (envelope-from krion@voodoo.oberon.net) Received: from krion by voodoo.oberon.net with local (Exim 4.43 (FreeBSD)) id 1CpPdm-000MB2-OZ; Fri, 14 Jan 2005 12:29:18 +0100 Date: Fri, 14 Jan 2005 12:29:18 +0100 From: Kirill Ponomarew To: Adi Pircalabu Message-ID: <20050114112918.GF69532@voodoo.oberon.net> References: <20050113062739.GA28658@xor.obsecurity.org> <20050113180504.GA26064@xor.obsecurity.org> <20050114130404.250d6e26@apircalabu.dsd.ro> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="W18qbkTAGYos9/y6" Content-Disposition: inline In-Reply-To: <20050114130404.250d6e26@apircalabu.dsd.ro> X-NCC-Regid: de.oberon X-NIC-HDL: KP869-RIPE 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 11:29:45 -0000 --W18qbkTAGYos9/y6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. > - The port uses several other files (plugins, modules) which will be > updated from time to time. Also, new modules / plugins whose names could > not be initially listed in pkg-plist may be added, as well as existing > ones may be updated or even deleted. It's better to use ~/.your_port directory in such cases. -Kirill --W18qbkTAGYos9/y6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB560OQC1G6a60JuURAj+yAJ4yHfJ+ekS3Fvy2sVFCX8MWeslkJACeJjyW cWQ6AnxIxqWaFu0tQzcvGhs= =HegM -----END PGP SIGNATURE----- --W18qbkTAGYos9/y6--