From: Angelo Arrifano <miknix@gentoo.org>
To: Gentoo Developers Mailing List <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] [RFC] ebuild function to show package changelog
Date: Fri, 12 Mar 2010 16:16:05 +0100 [thread overview]
Message-ID: <1268406965.7397.40.camel@localhost> (raw)
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
next reply other threads:[~2010-03-12 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 15:16 Angelo Arrifano [this message]
2010-03-12 15:33 ` [gentoo-dev] [RFC] ebuild function to show package changelog William Hubbs
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=1268406965.7397.40.camel@localhost \
--to=miknix@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