From owner-freebsd-ports Tue Sep 4 5:47: 6 2001 Delivered-To: freebsd-ports@freebsd.org Received: from franklin.physics.purdue.edu (franklin.physics.purdue.edu [128.210.146.222]) by hub.freebsd.org (Postfix) with ESMTP id E4B7537B401; Tue, 4 Sep 2001 05:47:03 -0700 (PDT) Received: from physics.purdue.edu (curie.physics.purdue.edu [128.210.68.223]) by franklin.physics.purdue.edu (Postfix) with ESMTP id 345EA20F01; Tue, 4 Sep 2001 07:49:00 -0500 (EST) Received: by physics.purdue.edu (Postfix, from userid 12409) id 0C34B76; Tue, 4 Sep 2001 07:49:53 -0500 (EST) Date: Tue, 4 Sep 2001 07:49:52 -0500 From: Will Andrews To: "Brian T. Schellenberger" Cc: Martti Kuparinen , will@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: ports/30294: Can't unlock KDE Message-ID: <20010904074952.A30764@curie.physics.purdue.edu> Reply-To: Will Andrews Mail-Followup-To: "Brian T. Schellenberger" , Martti Kuparinen , will@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG References: <20010904091704.O27939-100000@server.nomadiclab.com> <01090403430201.19266@i8k.babbleon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <01090403430201.19266@i8k.babbleon.org>; from bts@babbleon.org on Tue, Sep 04, 2001 at 03:43:02AM -0400 X-Operating-System: FreeBSD 4.3-STABLE i386 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Sep 04, 2001 at 03:43:02AM -0400, Brian T. Schellenberger (bts@babbleon.org) wrote: > In general, somehow gathering up "critical messages" might be a nice feature > for ports. Yes, I agree. I'm sympathetic with Martti's position and wish there was a useful solution. However, there just isn't one. The only way to solve this problem would be for bsd.port.mk to check for PKGMESSAGE files in each port that is installed, and when the install operation for any of them is done, announce them to the user at the end of the entire operation. It's not all black and white, unfortunately. Sometimes people are just doing a "make configure" and suddenly this other thing is a dependency. Oops, now we have a 20-line pkg-message for that other thing that's now a dependency. It'll scroll the configure target on the previous port, etc... choices, choices.. > In this case, the default results from the install are (IMHO) particularly > useless, though, so perhaps instead of it just being a pkg-message, the port > could actually stop and prompt the user for a decision about whether or not > to chmod or, at least prompt him to acknowledge that he saw the message? That's another problem. Lots of people (including myself) already take it for granted that when you run a "make install" it will not prompt you for this sort of thing. We'd have to set the IS_INTERACTIVE bit on a lot more ports than we had previously... -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message