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 ) id 1Nq8Dk-0007fT-MN for garchives@archives.gentoo.org; Fri, 12 Mar 2010 17:00:20 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 80C96E09FE; Fri, 12 Mar 2010 17:00:17 +0000 (UTC) Received: from earth.farbfinsternis.net (earth.farbfinsternis.net [87.118.98.117]) by pigeon.gentoo.org (Postfix) with ESMTP id A1437E09B8 for ; Fri, 12 Mar 2010 17:00:05 +0000 (UTC) Received: from [192.168.178.23] (p4FD54535.dip0.t-ipconnect.de [79.213.69.53]) (using SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by earth.farbfinsternis.net (Postfix) with ESMTPSA id 04B137C003D for ; Fri, 12 Mar 2010 17:58:01 +0100 (CET) Message-ID: <4B9A730E.5090007@gentoo.org> Date: Fri, 12 Mar 2010 17:59:58 +0100 From: Matti Bickel User-Agent: Thunderbird 2.0.0.23 (X11/20090817) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] ebuild function to show package changelog References: <1268406965.7397.40.camel@localhost> In-Reply-To: <1268406965.7397.40.camel@localhost> X-Enigmail-Version: 0.95.7 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF8F51C5986CB79F4A6910FAB" X-Archives-Salt: b0b191d0-a472-4738-a5f0-323dcfab9dc2 X-Archives-Hash: 9f82bfb966865d6ce9d6a8bc1cfc6855 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF8F51C5986CB79F4A6910FAB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 ", 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. --------------enigF8F51C5986CB79F4A6910FAB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkuacw4ACgkQfNMcoUhJ7Gx2vQCgnQM6uXS+nXSi5qSLuZbhhNKu CuUAnAs4ugj5vM6o7FeICAPCpf5/zYwu =Df9I -----END PGP SIGNATURE----- --------------enigF8F51C5986CB79F4A6910FAB--