Gentoo Archives: gentoo-dev

From: Peter Volkov <pva@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [git migration] The problem of ChangeLog generation
Date: Tue, 13 Apr 2010 16:47:58
Message-Id: 1271177238.30596.85.camel@tablet
In Reply to: Re: [gentoo-dev] [git migration] The problem of ChangeLog generation by Nirbheek Chauhan
1 В Втр, 13/04/2010 в 17:18 +0530, Nirbheek Chauhan пишет:
2 > The traditional ChangeLog that is currently employed in gentoo-x86
3 > (and in other projects) is simply an ugly hack
4
5 The difference between gentoo-x86 ebuild ChangeLogs and ChangeLogs used
6 in other projects is that gentoo-x86 ChangeLog is more like NEWS file
7 that summarizes important (affecting package) changes. That is why
8 emerge -l was implemented. And that is why it's better to avoid typos
9 there (fix them), drop redundant messages like comment edits, empty
10 lines removal and etc...
11
12 > Think of it like this: if you make a typo in a commit message, or
13 > forget to add something; you can't change it after you've published
14 > the commit (cvs/svn commit or git push) to the world.
15
16 And then it's better to keep ChangeLogs. For developers it was never a
17 problem to script `echangelog "log" && repoman commit -m "log"` and
18 conflict resolution is really not that hard with git. In spirit of
19 Gentoo, it's better to write some tool to update Manifests after
20 conflict resolution instead of making ChangeLogs less useful for those
21 who uses them.
22
23
24 BTW as for profiles ChangeLogs... May be it's better to generate them.
25
26 --
27 Peter.

Replies