From owner-freebsd-ports@FreeBSD.ORG Sat Oct 16 22:08:33 2004 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 7C80E16A4CE for ; Sat, 16 Oct 2004 22:08:33 +0000 (GMT) Received: from mail.halls.colostate.edu (halls-mailgw.acns.colostate.edu [129.82.100.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AE1043D2F for ; Sat, 16 Oct 2004 22:08:33 +0000 (GMT) (envelope-from end@endif.cjb.net) Received: from zork (inge069131.halls.colostate.edu [129.82.69.131]) i9GM8UVa016718; Sat, 16 Oct 2004 16:08:30 -0600 Date: Sat, 16 Oct 2004 16:08:30 -0600 From: Robin Schoonover To: Michael Nottebrock Message-ID: <20041016160830.34115d03@zork> In-Reply-To: <200410162312.35392.michaelnottebrock@gmx.net> References: <20041016135618.00711a35@dolphin.local.net> <20041016141935.2d77ebea@dolphin.local.net> <20041016143203.7d20298a@dolphin.local.net> <200410162312.35392.michaelnottebrock@gmx.net> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version 0.71, clamav-milter version 0.71 X-Virus-Status: Clean cc: "Conrad J. Sabatier" cc: freebsd-ports@freebsd.org Subject: Re: Ports with no pkg-plist files 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: Sat, 16 Oct 2004 22:08:33 -0000 On Sat, 16 Oct 2004 23:12:32 +0200 Michael Nottebrock wrote: > On Saturday 16 October 2004 21:32, Conrad J. Sabatier wrote: > > > Just as a footnote: I personally would prefer to keep the pkg-plist > > files around. They greatly simplify the task of determining what > > files are provided by an uninstalled port (I use a script I wrote > > that takes advantage of these files for just this purpose, in fact). > > Seems like your script needs a rewrite then. pkg-plist isn't the > canonical way to provide the packing list, it's just the most simple > one. Some ports require something less simple, for some even having a > separate file is overkill. > I've noticed that the only way to make sure you get a plist is to do a "make install" and then look the installed +CONTENTS. You need to build the port because some ports don't know what their plist is until they've built themselves (www/firefox being one). You need to install because some ports generate the plist as part of the install step (databases/php-sqlrelay, devel/colorer and many others do it this way...) -- Robin Schoonover (aka End) # # The older a man gets, the farther he had to walk to school as a boy. #