From: Matti Bickel <mabi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] ebuild function to show package changelog
Date: Fri, 12 Mar 2010 17:59:58 +0100 [thread overview]
Message-ID: <4B9A730E.5090007@gentoo.org> (raw)
In-Reply-To: <1268406965.7397.40.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
Angelo Arrifano wrote:
> 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?
No, please don't. I'm okay with it if your mean "at the end of
emerge -u <atom>", but wouldn't it be pointless to see what changed
*after* you just installed the thing?
The reason i'm against it is the complexity involved. You need to pull
down the source (up to hunderts of megabytes for openoffice), run
src_unpack and eventually src_configure phases. Then you need to know
where to look and what to show.
But i agree it's cool to know what i will gain from my daily emerge run.
As an alternative, let the ebuild provide a variable that points to
upstreams online Changelog or something, so you as a human can go parse
it yourself. But then you could also just take the HOMEPAGE variable
that's already there.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2010-03-12 17:00 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
2010-03-12 15:51 ` Angelo Arrifano
2010-03-12 16:12 ` William Hubbs
2010-03-12 16:59 ` Matti Bickel [this message]
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=4B9A730E.5090007@gentoo.org \
--to=mabi@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