From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ebuild ChangeLog and emerge -l
Date: Mon, 23 May 2011 11:50:12 -0500 [thread overview]
Message-ID: <BANLkTinQRjoF9oUDO-ppA060po5WtYTEBg@mail.gmail.com> (raw)
In-Reply-To: <irdufn$14f$1@dough.gmane.org>
On Mon, May 23, 2011 at 10:29 AM, Nikos Chantziaras <realnc@arcor.de> wrote:
> When doing an update using the -l option of emerge, eg:
>
> emerge -uDNl world
>
> The ChangeLog entries that are displayed seem buggy to me. For example,
> sometimes a whole page worth of changes from a single ChangeLog is
> displayed, containing entries for ebuilds older than what is currently
> installed. Some other times it's less dramatic, but still contains stuff
> that should not show up.
You can also take a look at:
/usr/lib64/portage/pym/_emerge/resolver/output_helpers.py
It contains the regexp that is used to parse the changelogs and the
logic of what is shown and ignored.
prev parent reply other threads:[~2011-05-23 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 15:29 [gentoo-user] ebuild ChangeLog and emerge -l Nikos Chantziaras
2011-05-23 15:46 ` James Wall
2011-05-23 16:50 ` Paul Hartman [this message]
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=BANLkTinQRjoF9oUDO-ppA060po5WtYTEBg@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.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