From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1EPK21-0004Z5-C9 for garchives@archives.gentoo.org; Tue, 11 Oct 2005 13:19:01 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id j9BD97FX001435; Tue, 11 Oct 2005 13:09:07 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id j9BD7Scx007517 for ; Tue, 11 Oct 2005 13:07:28 GMT Received: from vms042pub.verizon.net ([206.46.252.42]) by smtp.gentoo.org with esmtp (Exim 4.43) id 1EPK00-0007Py-UE for gentoo-dev@lists.gentoo.org; Tue, 11 Oct 2005 13:16:56 +0000 Received: from mail.joat.com ([71.114.140.80]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0IO7000GV688DTH0@vms042.mailsrvcs.net> for gentoo-dev@gentoo.org; Tue, 11 Oct 2005 08:16:57 -0500 (CDT) Received: from localhost (cornholio.joat.com [127.0.0.1]) by mail.joat.com (Postfix) with ESMTP id 5F8A33DBB for ; Tue, 11 Oct 2005 09:16:56 -0400 (EDT) Received: from mail.joat.com ([127.0.0.1]) by localhost (mail.joat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10103-10 for ; Tue, 11 Oct 2005 09:16:34 -0400 (EDT) Received: from butthead.joat.com (butthead.joat.com [192.168.0.10]) by mail.joat.com (Postfix) with ESMTP for ; Tue, 11 Oct 2005 09:16:30 -0400 (EDT) Date: Tue, 11 Oct 2005 09:18:41 -0400 From: Dave Nebinger Subject: [gentoo-dev] Just another portage enhancement idea... To: gentoo-dev@lists.gentoo.org Message-id: <200510110918.41357.dnebinger@joat.com> Organization: Joat.com Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-disposition: inline X-Virus-Scanned: amavisd-new at joat.com User-Agent: KMail/1.8.2 X-Archives-Salt: 3cd93889-b9f9-4e37-acec-a8351e017016 X-Archives-Hash: 33adba2db2b810871dd89c31cab4443b This is probably the fifth time at least that I've been bitten by this... Portage is great in that it manages compiles for a bulk of applications (including dependencies) in one fell swoop. Yesterday I emerged gnome - that was it, just gnome, and it took care of the whole thing soup to nuts. Wahoo, and kudos to all of you who put in the work. But here's my issue... In emerging one of the 101 packages missing on my system for gnome, a little blurb flew buy that should have caught my attention, a message posted in the pkg_postinst() message indicating what I should do now that my installation has completed. That's well and good, but as it was one of only 101 other packages, that message quickly gets lost in the shuffle. So here's the enhancement: have portage collect all of these kinds of messages and display them after all of the emerging has completed. So here's my proposed enhancement: Before the call to pkg_postinst(), set a flag that causes einfo/ewarn/etc. to tee the output generated by the ebuild to /var/log/portage_postinst.log (or something configurable in make.conf, whatever). Preface the first generated line with the ${P} so we know what it's related to. After the pkg_postinst() method completes, clear the flag and other emerges can carry on as they need to. Had this kind of thing been in place, after emerging 101 packages I could go to the postinst log and see everything that I had to do, including the little blurb that I had missed before. Yes, I know folks are going to say that you can enable portage logging and look for messages that need to be taken care of. But I just emerged 101 new packages, have many emerge -ud worlds, etc. resulting in almost 2000 files out there in /var/log/portage. Talk about the needle in the haystack, there's not even some specific keywords I could grep on to hit on the relevant information. Understandably I don't know what you all will say about this. It seems like a great idea to me, and wouldn't appear to come with all the political issues that the 'extending the ebuild meta data' or some other issues that have come up recently. But I'll leave it to the rest of you to decide... -- gentoo-dev@gentoo.org mailing list