From owner-freebsd-ports Wed Mar 29 20: 7:18 2000 Delivered-To: freebsd-ports@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id E05AC37BB27; Wed, 29 Mar 2000 20:07:14 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca2-07.ix.netcom.com [205.186.212.7]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id XAA01463; Wed, 29 Mar 2000 23:07:11 -0500 (EST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id UAA13103; Wed, 29 Mar 2000 20:07:09 -0800 (PST) To: Kris Kennaway Cc: "David O'Brien" , ports@FreeBSD.org Subject: Re: pkg/SECURITY References: From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami) Date: 29 Mar 2000 20:07:09 -0800 In-Reply-To: Kris Kennaway's message of "Sun, 26 Mar 2000 15:55:28 -0800 (PST)" Message-ID: Lines: 34 X-Mailer: Gnus v5.7/Emacs 20.6 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: Kris Kennaway * On Sun, 26 Mar 2000, David O'Brien wrote: * * > On Sat, Mar 25, 2000 at 05:43:54PM -0800, Kris Kennaway wrote: * > > I've written patches which teach bsd.port.mk and pkg_foo about a * > > pkg/SECURITY (and +SECURITY) file which gets cat'ed to the user before * > > pre-fetch, after post-install, and at pkg_add time. * > * > How is that different than having a pkg/MESSAGE file and explicitly * > cat'ing it in pre-fetch, and post-install? * * Because pkg/MESSAGE might already exist, and it's for a separate * purpose. MESSAGE is often used for things like post-install configuration * options that must be done before the port can be used, which isn't * appropriate to display before compilation. Well, you can use pkg/MESSAGE for anything you want.... * My pkg/SECURITY change also prints it bracketed by a * * ****** SECURITY WARNING ****** * * line and adds a "Press ^C if this is not acceptable" when displaying in * pre-fetch. You can put those inside the message files too. :) * I think it's cleaner to have it separate to MESSAGES. Actually I think it's better to use a REQ file so you can make sure the user actually reads those stuff.... Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message