From owner-freebsd-ports Thu Dec 3 15:47:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13558 for freebsd-ports-outgoing; Thu, 3 Dec 1998 15:47:11 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13546 for ; Thu, 3 Dec 1998 15:47:08 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.7/8.7.3) id PAA07095; Thu, 3 Dec 1998 15:46:24 -0800 (PST) Date: Thu, 3 Dec 1998 15:46:24 -0800 (PST) Message-Id: <199812032346.PAA07095@vader.cs.berkeley.edu> To: chaos@ultra.net.au CC: ports@FreeBSD.ORG In-reply-to: (message from Simon Coggins on Thu, 3 Dec 1998 18:03:36 +1000 (EST)) Subject: Re: Another creation of ports question From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * What should you do when the port can create files in a directory it's * installed in and you have no control over what the filenames are that will * be created so you can't add them to PLIST (and it breaks big time when you * try and deinstall.) Put the filenames you know about in pkg/PLIST Then merge whatever you want to the file ${TMPPLIST} in post-install Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message