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-40013-garchives=archives.gentoo.org@lists.gentoo.org>) id 1NqA1z-0000rU-PM for garchives@archives.gentoo.org; Fri, 12 Mar 2010 18:56:25 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E431DE080C; Fri, 12 Mar 2010 18:56:15 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 47237E0803 for <gentoo-dev@lists.gentoo.org>; Fri, 12 Mar 2010 18:56:02 +0000 (UTC) Received: from [10.0.0.10] (unknown [81.193.81.254]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id ADFAC1B4115; Fri, 12 Mar 2010 18:55:58 +0000 (UTC) Subject: Re: [gentoo-dev] [RFC] ebuild function to show package changelog From: Angelo Arrifano <miknix@gentoo.org> To: gentoo-dev@lists.gentoo.org Cc: Matti Bickel <mabi@gentoo.org> In-Reply-To: <4B9A730E.5090007@gentoo.org> References: <1268406965.7397.40.camel@localhost> <4B9A730E.5090007@gentoo.org> Content-Type: text/plain; charset="UTF-8" Organization: Gentoo Linux (embedded) Date: Fri, 12 Mar 2010 19:59:57 +0100 Message-ID: <1268420397.5497.3.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 X-Mailer: Evolution 2.28.3.1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 04a538cd-f249-483f-ab69-208dfdcc3a6a X-Archives-Hash: e987705e23d8ba4afab839ec75da6ff1 On Sex, 2010-03-12 at 17:59 +0100, Matti Bickel wrote: > 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? Not pointless. If people don't read package changelogs/releasenotes, then it is highly probable they miss new features in the packages. > > 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. A ChangeLog in the root of the source dir. is almost mandatory in autotools distributions. Despite the existence of a somewhat standard format for ChangeLogs, it is not enforced leaving the need to parse all the crap they through at us. > > 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. > As Jeremy pointed out: "There is an optional <changelog> tag in metadata.xml." That really looks like a better solution and it is something I might start putting on the packages I maintain. -- Angelo Arrifano AKA MiKNiX Gentoo Embedded/OMAP850 Developer Linwizard Developer http://www.gentoo.org/~miknix http://miknix.homelinux.com