ebuild ChangeLog and emerge -l
On Mon, May 23, 2011 at 10:29 AM, Nikos Chantziaras <firstname.lastname@example.org> 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.
> The above seems to be the norm rather than the exception. *For example,
> right now I'm doing an update from llvm-2.9-r1 to llvm-2.9-r2, and emerge
> *23 May 2011; Bernard Cafarelli <email@example.com> +llvm-2.9-r2.ebuild,
> *Fix header for gcc 4.6, bug #365925
> *21 Apr 2011; Fabian Groffen <firstname.lastname@example.org> llvm-2.9-r1.ebuild,
> *Fix broken reference that I missed yesterday
This is pulled in because of the change to the live ebuild which
evaluates as a newer ebuild.
> *20 Apr 2011; Fabian Groffen <email@example.com> llvm-2.9-r1.ebuild,
> *Fix install_name_tooling
same as above.
> Is this normal? *Bug?