Gentoo Archives: gentoo-dev

From: Ulrich Mueller <ulm@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] ChangeLog generation, profiles/ mess.
Date: Wed, 30 Nov 2016 11:08:33
Message-Id: 22590.45822.182438.561189@a1i15.kph.uni-mainz.de
In Reply to: Re: [gentoo-dev] ChangeLog generation, profiles/ mess. by "Robin H. Johnson"
1 >>>>> On Tue, 29 Nov 2016, Robin H Johnson wrote:
2
3 >> - one ChangeLog for each first-level subdir other than categories
4 >> (i.e. eclass, licenses, profiles, etc.),
5 > Already done, just querying if profiles/ needs more ChangeLog detail.
6
7 Yeah, keep one ChangeLog for all of profiles/. The existing
8 sub-ChangeLogs there are rather confusing because they don't seem to
9 follow any consistent layout.
10
11 Keeping one single file would also agree with the recommendation for
12 commit messages, namely to prepend "profiles:" for any change below
13 the profiles/ dir.
14 https://wiki.gentoo.org/wiki/Gentoo_git_workflow#Commit_message_format
15
16 > Here's the size of the non-category non-package changelogs, with
17 > splitting to all top-levels.
18 > 127 scripts/ChangeLog-2016
19 > 1266 metadata/ChangeLog-2016
20 > 1929 ChangeLog-2016
21 > 11987 licenses/ChangeLog-2016
22 > 198021 eclass/ChangeLog-2016
23 > 362733 profiles/ChangeLog-2016
24
25 > If we collapse to have:
26 > - per-package
27 > - major top-levels: eclass/, profile/, licenses/
28 > - (everything else)
29 > Then we get:
30 > 11972 licenses/ChangeLog-2016
31 > 12941 ChangeLog-2016
32 > 196905 eclass/ChangeLog-2016
33 > 362040 profiles/ChangeLog-2016
34
35 I like the second scheme better. (No strong opinion about keeping
36 separate ChangeLogs for metadata/ and scripts/ though.)
37
38 Ulrich