Re: [STUMP] Should the upstream ChangeLog be included in a snapshot package?

[Luca Capello]

Hi there!

On Fri, 18 Jul 2008 11:13:45 +0200, Shawn wrote:
> Luca Capello <address@hidden> writes:
>> Since the ChangeLog file has been replaced by the output of `git log`, I
>> was asking myself if the Debian package should include it or not,
>> assuming that I'm not packaging a released version, but a Git snapshot
>> instead.
[...]
> It makes sense to me to include a ChangeLog generated from git log.

The process I chose to include the upstream ChangeLog is a bit tricky,
but it works, let me explain it :-)

1) as I already wrote before, I prefer to package a Git checkout, which
   lacks the ChangeLog

2) given the nature of the Debian package building process, upstream
   sources are in a .orig.tar.gz file and Debian modifications in a
   .diff.gz one

3) since I manage the Debian package directly in Git (thanks to
   git-buildpackage [1]), I'd like to avoid any difference with the
   upstream Git repository

4) the simplest solution I found is to ship the upstream ChangeLog as a
   Debian patch [2], which will be updated every time the upstream
   'master' Git branch will be merged into the 'debian' one [3]

5) the result for the end-user is that the upstream ChangeLog is
   included in /usr/share/doc/stumpwm/changelog.gz :-D

Thx, bye,
Gismo / Luca

Footnotes: 
[1] http://packages.debian.org/git-buildpackage
[2] 
http://git.debian.org/?p=pkg-common-lisp/stumpwm.git;a=commitdiff;h=bdf626896d9144569737ad76fd3bb1f7553d9f4c
[3] http://git.debian.org/?p=pkg-common-lisp/stumpwm.git;a=summary

pgpdKgDXa_Khj.pgp
Description: PGP signature