public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "András Csányi" <sayusi.ando@sayusi.hu>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] KDE and NetworkManager
Date: Fri, 19 Jul 2013 10:24:35 +0200	[thread overview]
Message-ID: <CALzub=rDGiFFRApML2bQVq1hDNb433g9s-1=Ni0Gr5MYbgVrOw@mail.gmail.com> (raw)
In-Reply-To: <20130719091715.0ac00ddb@hactar.digimed.co.uk>

On 19 July 2013 10:17, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Fri, 19 Jul 2013 09:35:52 +0200, András Csányi wrote:
>
>> >> >> 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.
>
>> When I sad that to read the ebuild is not user friendly I thought of
>> that it should be a better solution to get post install message than
>> open the ebuild and read it. The elogv is fine for me.
>
> Elogv is a log viewer, you specifically stated that you did not wish to
> read the log files, hence the "read the ebuild" suggestion.

Yes, you are right. I wrote that. The meaning of that was:
- I don't want to open a log file manually
- I don't want to browse the log file to find what I need
- I don't want to burn my time to put raw the information into context
in order to it would be easy to understand

Elogv does what I described above for me. This is the reason why I say
that it is perfect for me.

> Although I have portage save the logs, I rarely look at them because I
> also have it mail them to me. That way they are easy to read and hard to
> ignore.

--
--  Csanyi Andras (Sayusi Ando)  -- http://sayusi.hu --
http://facebook.com/andras.csanyi
--  ""Trust in God and keep your gunpowder dry!" - Cromwell


  reply	other threads:[~2013-07-19  8:24 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 [this message]
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='CALzub=rDGiFFRApML2bQVq1hDNb433g9s-1=Ni0Gr5MYbgVrOw@mail.gmail.com' \
    --to=sayusi.ando@sayusi.hu \
    --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