From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-dev+bounces-39995-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1Nq6XI-0006mp-Mr
	for garchives@archives.gentoo.org; Fri, 12 Mar 2010 15:12:24 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 6C5A4E0B43;
	Fri, 12 Mar 2010 15:12:20 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
	by pigeon.gentoo.org (Postfix) with ESMTP id 30F4DE073A
	for <gentoo-dev@lists.gentoo.org>; Fri, 12 Mar 2010 15:12:05 +0000 (UTC)
Received: from [10.0.0.10] (unknown [81.193.81.254])
	(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.gentoo.org (Postfix) with ESMTP id D617C1B410E
	for <gentoo-dev@lists.gentoo.org>; Fri, 12 Mar 2010 15:12:03 +0000 (UTC)
Subject: [gentoo-dev] [RFC] ebuild function to show package changelog
From: Angelo Arrifano <miknix@gentoo.org>
To: Gentoo Developers Mailing List <gentoo-dev@lists.gentoo.org>
Content-Type: text/plain; charset="UTF-8"
Organization: Gentoo Linux (embedded)
Date: Fri, 12 Mar 2010 16:16:05 +0100
Message-ID: <1268406965.7397.40.camel@localhost>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
Mime-Version: 1.0
X-Mailer: Evolution 2.28.2 
Content-Transfer-Encoding: 7bit
X-Archives-Salt: 978bd037-e862-4543-b85a-71c5cd94ff40
X-Archives-Hash: 2f13f2cc140a9a4c68070f7f7824288c

Hello all,

[Speaking as user] I find myself many times stumbling through package
ChangeLogs to see what is new/changed after a emerge -u world. As some
of you might agree, this is time consuming.

What do you people think on a new pkg_changelog function that would
instruct the ebuild how to retrieve this kind of information from the
package? Most of packages have a somewhat standard place for it in the
source tree, so I guess a default pkg_changelog function could, in
theory, be implemented.

This function could be then called at user request by means of e.g.
emerge --showchangelog <atom> or at the end of emerge update (controlled
through a FEATURES="show-changelog" or something).

I know we are all busy with a lot of things and I know what Gentoo don't
really need right now is more cruft in the ebuilds (just think on QA!).

Regards,
-- 
Angelo Arrifano AKA MiKNiX
Gentoo Embedded/OMAP850 Developer
Linwizard Developer
http://www.gentoo.org/~miknix
http://miknix.homelinux.com