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-40001-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1Nq7Th-0003jb-4P
for garchives@archives.gentoo.org; Fri, 12 Mar 2010 16:12:45 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id EAF32E0AAC;
Fri, 12 Mar 2010 16:12:39 +0000 (UTC)
Received: from qw-out-1920.google.com (qw-out-1920.google.com [74.125.92.149])
by pigeon.gentoo.org (Postfix) with ESMTP id 8BACFE0A07
for <gentoo-dev@lists.gentoo.org>; Fri, 12 Mar 2010 16:12:23 +0000 (UTC)
Received: by qw-out-1920.google.com with SMTP id 14so394110qwa.10
for <gentoo-dev@lists.gentoo.org>; Fri, 12 Mar 2010 08:12:23 -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=8MAWtc9I3SAgu5ppzCd7PfhmKukYJeJAJgla1cAoyjY=;
b=ZI1VmB27RjFBkdGy7LP2z8Iw3hHR8+azYyAAzl1GQDetY6gnRbfhCoQfIRnAUTTxYr
qmjvaUKzmIKcZRhbfS+ACxlvCNJHfyIh3OnlYw3Y/J9ApOHAiTAz5kNtnRuz5sUeYABj
vxBLpttPMT4imm2Z28tVa8VCDc0rzP3sqi6HA=
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=THkCCe5jXy0Mp09oFO36UgAs0vzKByxwKtowMsLHbfeXqVr6LYboKqSZcyOxMWxaV1
o2Atrytg4E05vtEct05QCEPj7UImBFB4PJO/FOAfNVoBD8NuZC/4q+V9crDEmo9KNdqH
4gTfMuqCIQem9kP3k4RSzlAtzEhGGkKt8xjwU=
Received: by 10.220.127.96 with SMTP id f32mr1268533vcs.152.1268410337857;
Fri, 12 Mar 2010 08:12:17 -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 15sm448407yxh.22.2010.03.12.08.12.15
(version=SSLv3 cipher=RC4-MD5);
Fri, 12 Mar 2010 08:12:16 -0800 (PST)
Sender: William Hubbs <w.d.hubbs@gmail.com>
Received: by linux1 (sSMTP sendmail emulation); Fri, 12 Mar 2010 10:12:14 -0600
Date: Fri, 12 Mar 2010 10:12:14 -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: <20100312161214.GA4132@linux1>
Mail-Followup-To: gentoo-dev@lists.gentoo.org
References: <1268406965.7397.40.camel@localhost>
<20100312153350.GA3970@linux1>
<1268409062.7397.50.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="bp/iNruPH9dso1Pn"
Content-Disposition: inline
In-Reply-To: <1268409062.7397.50.camel@localhost>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Archives-Salt: 8527f05f-e534-4177-bfbf-a26625402f5f
X-Archives-Hash: 1ed8208d19370469ebb0c74da97f52e2
--bp/iNruPH9dso1Pn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Mar 12, 2010 at 04:51:02PM +0100, Angelo Arrifano wrote:
> On Sex, 2010-03-12 at 09:33 -0600, William Hubbs wrote:
> > 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 (control=
led
> > > 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.
>=20
> For a moment, you really tricked me into believing I've been missing
> this feature. Specially by reading man emerge:
> "This will show the ChangeLog entries for all the packages"
> btw: shouldn't it read "ebuilds" here? /\
To me, if you change that wording to "ebuilds", you mean there will be a
separate changelog for each *.ebuild file, so I would disagree with this
change.
> What I meant originally was to show the ChangeLog of the package
> (ChangeLog inside source tree), not the ebuild ChangeLog.
Not all upstreams provide changelogs (take a look at openrc as an
example), so I'm not sure we could do this. Also, if we did, which file
should we show (ChangeLog, NEWS, README ?) and how much of the file
should we show?
I'm not sure that there is an easy way to implement something like this.
William
--bp/iNruPH9dso1Pn
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
iEYEARECAAYFAkuaZ94ACgkQblQW9DDEZTikjQCgknYN4ZMwU1OSkgd/mzokLLO4
x/oAn0w12q7a9j/Pnkxx+YxqoOTejitL
=x+3p
-----END PGP SIGNATURE-----
--bp/iNruPH9dso1Pn--