From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] ebuild function to show package changelog
Date: Fri, 12 Mar 2010 09:33:50 -0600 [thread overview]
Message-ID: <20100312153350.GA3970@linux1> (raw)
In-Reply-To: <1268406965.7397.40.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On Fri, Mar 12, 2010 at 04:16:05PM +0100, Angelo Arrifano wrote:
> 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).
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
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-12 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 15:16 [gentoo-dev] [RFC] ebuild function to show package changelog Angelo Arrifano
2010-03-12 15:33 ` William Hubbs [this message]
2010-03-12 15:51 ` Angelo Arrifano
2010-03-12 16:12 ` William Hubbs
2010-03-12 16:59 ` Matti Bickel
2010-03-12 17:14 ` Jeremy Olexa
2010-03-12 17:26 ` Matti Bickel
2010-03-12 18:59 ` Angelo Arrifano
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=20100312153350.GA3970@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-dev@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