Re: original package changelogs

2010-01-27 Thread The Fungi
On Sun, Jan 10, 2010 at 10:58:01PM +0800, Paul Wise wrote: [...] > If you use a version control system, there are cvs2cl, svn2cl, git2cl > and probably other scripts to convert your commit messages into > GNU-style ChangeLog files, no need to reinvent the wheel here. [...] I did anyway--using GitP

Re: original package changelogs

2010-01-11 Thread Tim Retout
On Sun, 2010-01-10 at 14:00 +, Seger, Mark wrote: > Is there any standard (or desired format). Since I intend to include > both my release notes and an automatically generated changelog, it > should be pretty easy to create the log headers in any format people > would like to see. As an up

Re: original package changelogs

2010-01-10 Thread Russ Allbery
Paul Wise writes: > On Mon, Jan 11, 2010 at 6:02 AM, Russ Allbery wrote: >> There's an open Policy bug about this, which is where it should probably >> be discussed.  When packaging other people's software, I install the >> upstream ChangeLog as changelog.gz and NEWS as NEWS.gz. > For some pack

Re: original package changelogs

2010-01-10 Thread Paul Wise
On Mon, Jan 11, 2010 at 6:02 AM, Russ Allbery wrote: > There's an open Policy bug about this, which is where it should probably > be discussed.  When packaging other people's software, I install the > upstream ChangeLog as changelog.gz and NEWS as NEWS.gz. For some packages where upstream ignore

Re: original package changelogs

2010-01-10 Thread Russ Allbery
Ben Finney writes: > Russ Allbery writes: >> All of the packages for which I'm both upstream and the Debian packager >> have no traditional ChangeLog file, only NEWS, and install the upstream >> NEWS file as /usr/share/doc//changelog.gz. > Perhaps that could be made clear; it's surely an obviou

Re: original package changelogs

2010-01-10 Thread Ben Finney
Russ Allbery writes: > I think NEWS is far and away the more useful of the two files. Usually > the full changelog has an overwhelming amount of detail and isn't > horribly useful at answering users' questions. How would you relate this valuation against the Lintian checks? Should Lintian care l

Re: original package changelogs

2010-01-10 Thread Ben Finney
Paul Wise writes: > If you use a version control system, there are cvs2cl, svn2cl, git2cl > and probably other scripts to convert your commit messages into > GNU-style ChangeLog files, no need to reinvent the wheel here. For Bazaar, this is an option to the ‘log’ command: bzr log --log-form

Re: original package changelogs

2010-01-10 Thread Russ Allbery
Paul Wise writes: > Please be aware of the difference between NEWS files and ChangeLog files > in the GNU coding standards document. Most upstreams completely ignore > this difference. GNU NEWS[3] files are a list of user-visible changes > for each release. The GNU coding standards document doesn

Re: original package changelogs

2010-01-10 Thread Yavor Doganov
Some additional comments from me that may or may not be worth reading. Paul Wise wrote: > The GNU coding standards document doesn't recommend any specific > format for NEWS files. Right -- the format is (and has always been) free-form; it's usually a nested list suitable for Emacs' outline-mode.

Re: original package changelogs

2010-01-10 Thread Pietro Battiston
Il giorno dom, 10/01/2010 alle 22.58 +0800, Paul Wise ha scritto: > I assume you are talking about the upstream ChangeLog rather than > debian/changelog. > > The only standard I am aware of for that is the one described in the > GNU coding standards document[1]. The suggested document doesn't men

Re: original package changelogs

2010-01-10 Thread Paul Wise
I assume you are talking about the upstream ChangeLog rather than debian/changelog. The only standard I am aware of for that is the one described in the GNU coding standards document[1]. Many upstreams completely ignore it and the recommended file naming (ChangeLog not CHANGES.TXT or one of the ot