From sethfalcon at gmail.com  Sat Sep 10 17:32:11 2005
From: sethfalcon at gmail.com (Seth Falcon)
Date: Sat, 10 Sep 2005 08:32:11 -0700
Subject: [Rd] Issue tracking in packages
In-Reply-To: <17186.46037.468981.530188@mithrandir.hornik.net> (Kurt Hornik's
	message of "Sat, 10 Sep 2005 12:22:13 +0200")
References: <3.0.6.32.20050909015829.007bed60@pop.gmx.net>
	<3.0.6.32.20050909145010.007c2a70@pop.gmx.net>
	<Pine.LNX.4.63a.0509090845050.619@homer23.u.washington.edu>
	<971536df05090910211d639ed1@mail.gmail.com>
	<Pine.LNX.4.63a.0509091029550.5570@homer23.u.washington.edu>
	<971536df05090910442796d89d@mail.gmail.com>
	<Pine.LNX.4.63a.0509091250220.5570@homer23.u.washington.edu>
	<17186.46037.468981.530188@mithrandir.hornik.net>
Message-ID: <m2mzml2b2c.fsf@macaroni.gateway.2wire.net>

On 10 Sep 2005, Kurt.Hornik at wu-wien.ac.at wrote:
> I like the suggestion about using a Changelog (or whatever it would
> be called) field in the package DESCRIPTION meta-data.  If we have
> that, we could not only use this for repository-side presentation of
> the package, but also install such info and have a simple
> show_package_change_log() function ...

For what its worth, I don't like this idea of adding a ChangeLog field
to the DESCRIPTION file.

Agreeing upon a standard location for NEWS or CHANGES or some such
seems a more simple solution.  As long as the presence of such a file
is *optional*.  And if the location really needs to be at the top,
then the build tools could grab it from there as they do the
DESCRIPTION file.

+ seth



[Rd] Issue tracking in packages
Seth Falcon