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-39996-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1Nq6uQ-0000jq-R6
for garchives@archives.gentoo.org; Fri, 12 Mar 2010 15:36:19 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id C87ADE0B05;
Fri, 12 Mar 2010 15:36:16 +0000 (UTC)
Received: from qw-out-1920.google.com (qw-out-1920.google.com [74.125.92.148])
by pigeon.gentoo.org (Postfix) with ESMTP id 2103FE0AA7
for <gentoo-dev@lists.gentoo.org>; Fri, 12 Mar 2010 15:36:09 +0000 (UTC)
Received: by qw-out-1920.google.com with SMTP id 14so383737qwa.10
for <gentoo-dev@lists.gentoo.org>; Fri, 12 Mar 2010 07:36:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:received:received:sender:received:date:from:to
:subject:message-id:mail-followup-to:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
bh=MZJMvjFlFrFHUzMXe8Umbm+4wDxjI5pWT2ikY+Aj/xw=;
b=AJ8W4rtt94V0VU700+oNmp9DqXfceXhtTa8i/srowgtBjrVYW89ad6ghCYbm6CcNua
hor/PLiazG1nnoi8MYlVwk2o5mGRkZHDIgef46gyVJh0F5oWHufdwuFt24owo/SK/Yur
bVOJ//xW6C/BM3GRzCHdw7NpKGA2prtqkWdio=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=sender:date:from:to:subject:message-id:mail-followup-to:references
:mime-version:content-type:content-disposition:in-reply-to
:user-agent;
b=W4Y4kR4/AShTGqBUrjZ7TOxLrFVubLutdxdhG/akdwqxSrUXCZkAZQGKvL27rjOT1q
Cye8UoBJNEmgZb8++YvDWEZi/VDfNHDETKbH+m8IblZiLRtdGc9LR+oaN4W63XZjVJZo
0Kg8yf8smSfrM32v8CApe2GnGyGRrHyGAGvoI=
Received: by 10.220.124.170 with SMTP id u42mr18588vcr.50.1268408036263;
Fri, 12 Mar 2010 07:33:56 -0800 (PST)
Received: from linux1 (cpe-76-183-49-63.tx.res.rr.com [76.183.49.63])
by mx.google.com with ESMTPS id 6sm435407yxg.12.2010.03.12.07.33.51
(version=SSLv3 cipher=RC4-MD5);
Fri, 12 Mar 2010 07:33:53 -0800 (PST)
Sender: William Hubbs <w.d.hubbs@gmail.com>
Received: by linux1 (sSMTP sendmail emulation); Fri, 12 Mar 2010 09:33:50 -0600
Date: Fri, 12 Mar 2010 09:33:50 -0600
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] ebuild function to show package changelog
Message-ID: <20100312153350.GA3970@linux1>
Mail-Followup-To: gentoo-dev@lists.gentoo.org
References: <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
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z"
Content-Disposition: inline
In-Reply-To: <1268406965.7397.40.camel@localhost>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Archives-Salt: a37e8408-05cf-42ff-936b-9f13188469ec
X-Archives-Hash: 2dc21239d3b0dd8f9381c5411d203861
--Nq2Wo0NMKNjxTN9z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Mar 12, 2010 at 04:16:05PM +0100, Angelo Arrifano wrote:
> Hello all,
>=20
> [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.
>=20
> 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.
>=20
> 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=3D"show-changelog" or something).
=20
Actually there is already an option for emerge to show the changelogs
of packages that will be upgraded. Take a look at the --changelog
option for emerge. It can be used along with --pretend to show you the
changelogs of packages that will be upgraded.
Thanks,
William
--Nq2Wo0NMKNjxTN9z
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
iEYEARECAAYFAkuaXt4ACgkQblQW9DDEZTjTEACfU+6nSaTvkJaaZNoxqav+hCBn
6OcAn1y8VZIewG661RnUbWiGzzAiRGEA
=RwPA
-----END PGP SIGNATURE-----
--Nq2Wo0NMKNjxTN9z--