stumpwm-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Luca Capello
Subject: [STUMP] Should the upstream ChangeLog be included in a snapshot package?
Date: Fri, 18 Jul 2008 01:49:05 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)

Hi all!

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.

The major problem is that the ChangeLog should be manually generated:
it's true that the Debian package reflects a Git snapshot, but once the
source package enters Debian, it doesn't contain anymore the .git
folder.  This means that if someone wants to grab the Debian sources and
build the package, she/he cannot rely anymore on any `git` command.

This situation is very similar to other software whose authors prefer
the VCS log instead of a manually edited ChangeLog: other examples are
Conkeror [1] or the BESE software [2], for which there's no upstream
ChangeLog in the Debian packages.

Suggestions?

Thx, bye,
Gismo / Luca

Footnotes: 
[1] http://conkeror.org
[2] http://common-lisp.net/project/bese/

Attachment: pgpcGBP_cUjlS.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]