public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE and NetworkManager
Date: Wed, 17 Jul 2013 08:03:29 -0500	[thread overview]
Message-ID: <20130717130329.GN3387@server> (raw)
In-Reply-To: <CALzub=o8CCv7-2shkPfDB_FXaQ2qEhT4mX3YDUH+DniBZJEh2g@mail.gmail.com>

On Wed, Jul 17, 2013 at 02:18:22PM +0200, András Csányi wrote:
> On 17 July 2013 13:59, Bruce Hill <daddy@happypenguincomputers.com> wrote:
> > On Wed, Jul 17, 2013 at 10:04:12AM +0200, András Csányi wrote:
> >> >
> >> > mingdao@jeremiah ~ $ grep plugdev /usr/portage/net-misc/wicd/wicd-1.7.2.4-r*
> >> > mingdao@jeremiah ~ $ grep users /usr/portage/net-misc/wicd/wicd-1.7.2.4-r*
> >> > /usr/portage/net-misc/wicd/wicd-1.7.2.4-r2.ebuild:              ewarn "Wicd-1.6 and newer requires your user to be in the 'users' group. If"
> >> > /usr/portage/net-misc/wicd/wicd-1.7.2.4-r3.ebuild:              ewarn "Wicd-1.6 and newer requires your user to be in the 'users' group. If"
> >>
> >> Ok. How is possible to get the post-install message of an ebuild
> >> without re-emerge the package neither opening the log file? The man
> >> page of emerge cannot say anything about it.
> >
> > Read the pkg_postinst portion of the ebuild.
> 
> Great!
> 
> > If you have installed app-portage/elogv issue "elogv" and find the desired
> > package.
> 
> Thanks, I'll check it!
> 
> > Two quick ways off the top of my head after the first cup of coffee. ;)
> 
> The magic is coming from coffee, I know! :)

Since reading the ebuild is not the _friendly_ way to get this information,
let me help you install the software to make this easy...

emerge -ajv app-portage/elogv (ncurses, which is text with colors)
or
emerge -ajv app-portage/elogviewer (GTK+ based utility, perhaps with GUI)

Now add these lines to /etc/portage/make.conf (/etc/make.conf on old systems)

PORTAGE_ELOG_SYSTEM="save"
PORTAGE_ELOG_CLASSES="warn error info log qa"

Then create this directory as root with this command:

mkdir -p /var/log/portage/elog

Then as root add your normal user to the portage group with this command:

gpasswd -a <username> portage (replace <username> with your normal user's name
and do not use the < >

Then issue:

newgrp

as that user or logout of Linux and log back in (you do _not_ need to reboot).

Then you can issue "elogv" or start elogviewer from the desktop entry and read
the logs of your files.

Hope this helps.

Happy Gentooing!

Bruce
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.                                                                                                                                                          
Q: Why is top-posting such a bad thing?                                                                                                                                                                                        
A: Top-posting.                                                                                                                                                                                                                
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting


  reply	other threads:[~2013-07-17 13:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 16:44 [gentoo-user] KDE and NetworkManager András Csányi
2013-07-15 18:26 ` Alan McKinnon
2013-07-15 19:08   ` Canek Peláez Valdés
2013-07-16 12:16     ` Todd Goodman
2013-07-16 12:31       ` Bruce Hill
2013-07-16 16:59     ` András Csányi
2013-07-16 17:09       ` Canek Peláez Valdés
2013-07-16 18:20         ` Bruce Hill
2013-07-16 18:47           ` Stroller
2013-07-16 19:21             ` Bruce Hill
2013-07-17  8:04           ` András Csányi
2013-07-17  8:12             ` Алексей Мишустин
2013-07-17  8:15               ` Алексей Мишустин
2013-07-17  9:35             ` Neil Bothwick
2013-07-17 11:39               ` András Csányi
2013-07-17 12:35                 ` Neil Bothwick
2013-07-17 12:42                   ` András Csányi
2013-07-17 12:49                 ` Bruce Hill
2013-07-19  7:35                   ` András Csányi
2013-07-19  8:17                     ` Neil Bothwick
2013-07-19  8:24                       ` András Csányi
2013-07-17 11:59             ` Bruce Hill
2013-07-17 12:18               ` András Csányi
2013-07-17 13:03                 ` Bruce Hill [this message]
2013-07-17 13:46                   ` Neil Bothwick
2013-07-19  7:16                   ` András Csányi
2013-07-16 17:43       ` Alan McKinnon
2013-07-16 18:44         ` András Csányi
2013-07-16 18:13       ` Bruce Hill
2013-07-15 19:03 ` Andrés Becerra Sandoval

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130717130329.GN3387@server \
    --to=daddy@happypenguincomputers.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox