From: "Алексей Мишустин" <shumkar@shumkar.ru>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE and NetworkManager
Date: Wed, 17 Jul 2013 12:12:10 +0400 [thread overview]
Message-ID: <CAGWFrgtufZK7p5-Rf83TJf4=0uJh5GbONR52CPMmzDB4nQUZTw@mail.gmail.com> (raw)
In-Reply-To: <CALzub=qYoyFX58foAo6j4u+SCgPTbaRN_OAv7d6QcYWtxvrkmg@mail.gmail.com>
2013/7/17 András Csányi <sayusi.ando@sayusi.hu>:
> On 16 July 2013 20:20, Bruce Hill <daddy@happypenguincomputers.com> wrote:
>> On Tue, Jul 16, 2013 at 12:09:46PM -0500, Canek Peláez Valdés wrote:
>>>
>>> The ebuild says it:
>>>
>>> src_prepare() {
>>> DOC_CONTENTS="To modify system network connections without needing
>>> to enter the
>>> root password, add your user account to the 'plugdev'
>>> group."
>>>
>>> When you install it, a message appears with that text.
>>
>> Which wicd-version ebuild did you pull _that_ text from?
>>
>> 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.
There are 2 programs reading emerge log files and displaying them in
an aesy format: elogv (ncurses) and elogviwer (X).
It is necessary to have the variables PORTAGE_ELOG_CLASSES and
PORTAGE_ELOG_SYSTEM set properly for get these program to work, for
example:
PORTAGE_ELOG_CLASSES="warn error log"
PORTAGE_ELOG_SYSTEM="save"
--
Regards,
Alex
next prev parent reply other threads:[~2013-07-17 8:12 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 ` Алексей Мишустин [this message]
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
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='CAGWFrgtufZK7p5-Rf83TJf4=0uJh5GbONR52CPMmzDB4nQUZTw@mail.gmail.com' \
--to=shumkar@shumkar.ru \
--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