Date: Tue, 23 Oct 2001 00:58:12 -0400 (EDT) From: Igor Roshchin <str@giganda.komkon.org> To: ghelmer@palisadesys.com, scanner@jurai.net, will@physics.purdue.edu Cc: kde@FreeBSD.ORG, ports@FreeBSD.ORG, security@FreeBSD.ORG Subject: RE: your mail Message-ID: <200110230458.f9N4wCX13835@giganda.komkon.org> In-Reply-To: <HEEHKIJOHDLFOOEBABJIEEHMCAAA.ghelmer@palisadesys.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> From owner-freebsd-security@FreeBSD.ORG Fri Oct 19 13:33:02 2001 > From: "Guy Helmer" <ghelmer@palisadesys.com> > To: "Will Andrews" <will@physics.purdue.edu>, <scanner@jurai.net> > Cc: <security@FreeBSD.ORG>, <ports@FreeBSD.ORG>, <kde@FreeBSD.ORG> > Subject: RE: your mail > Date: Fri, 19 Oct 2001 12:36:15 -0500 > > > On Friday, October 19, 2001 12:16 PM, Will Andrews wrote: > > On Fri, Oct 19, 2001 at 01:15:31PM -0400, scanner@jurai.net wrote: > > > I think the actual problem isn't so much the message per se, > > its the fact > > > its placed in the wrong place. It should be shown at the *end* of the > > > build instead of during the building of kdebase. When you go to > > build the > > > metaport of KDE2 no one wants to sit there watching the output for 12 > > > hours while it builds. They want to come back and see the familiar > > > "everything built ok" and then install it. If you place it as > > the message > > > at the end of the build *alot* more people would see the > > > message. Otherwise no one is going to catch it. Just my $.02. > > > > Yeah, I'm aware of that. Unfortunately, there is nothing I can > > do about that, because people might be invoking the kdebase port > > from anywhere. So it's a general ports problem. :\ > > How about sending an email message to "root" with this message? It solves > the problem of the message scrolling by during the installation... > I don't think I'd always want to have an e-mail message sent to root or to the building user. Probably, it can be an option, but not a default one. Talking about "general ports problem": script(1) is a good solution in this situation. It allows one to record all output, including warnings and such. Regards, Igor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110230458.f9N4wCX13835>