From owner-freebsd-ports-bugs Mon Jan 20 8:40:10 2003 Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7A0F37B401 for ; Mon, 20 Jan 2003 08:40:08 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E9B743F7C for ; Mon, 20 Jan 2003 08:40:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h0KGe2NS086522 for ; Mon, 20 Jan 2003 08:40:02 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h0KGe2j2086521; Mon, 20 Jan 2003 08:40:02 -0800 (PST) Date: Mon, 20 Jan 2003 08:40:02 -0800 (PST) Message-Id: <200301201640.h0KGe2j2086521@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Cc: From: Kenneth Stailey Subject: Re: ports/47254: pkg-name is not a generated file Reply-To: Kenneth Stailey Sender: owner-freebsd-ports-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR ports/47254; it has been noted by GNATS. From: Kenneth Stailey To: Simon 'corecode' Schubert Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: ports/47254: pkg-name is not a generated file Date: Mon, 20 Jan 2003 08:30:23 -0800 (PST) I just noticed that the title of this pr should say "pkg-message" not "pkg-name". The message body is correct. --- Simon 'corecode' Schubert wrote: > Lately Kenneth Stailey told: > > > But pkg-message is a committed file. > > > > http://www.freebsd.org/cgi/cvsweb.cgi/ports/emulators/klh10/pkg-message > > > > Why generate it at pre-install time when you've already downloaded it with > > cvs/cvsup? > > either stick with the existing file, that's easy > or create it every time and have an always-valid path in the message. > > in this context your patch seems okay then. you should then modify > pkg-message to contain a generic path. > > cheers > simon Here is the documentation about pkg-message: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/pkg-files.html << 12.1 pkg-message If you need to display a message to the installer, you may place the message in pkg-message. This capability is often useful to display additional installation steps to be taken after a pkg_add or to display licensing information. Note: The pkg-message file does not need to be added to pkg-plist. Also, it will not get automatically printed if the user is using the port, not the package, so you should probably display it from the post-install target yourself. >> So what is this about a generic path? How does it work? Can the handbook be made more clear? I display the message from the port's Makefile using echo of static strings not cat of the pkg-message file. The pkg-message file is only for binary packages not a source code port; it's not port-message, it's pkg-message. Thanks, Ken __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports-bugs" in the body of the message