1 |
All, |
2 |
|
3 |
This message is probably more interesting for developers, than it is for |
4 |
users, but since users directly "benefit" from this change, it should be |
5 |
of interest to most. |
6 |
|
7 |
Since yesterday, all of the ChangeLog files in the prefix rsync tree are |
8 |
generated from the CVS and SVN commit messages. This means the checked |
9 |
in ChangeLog files are discarded and overwritten by the generated |
10 |
versions when rsync0 assembles the rsync tree. |
11 |
|
12 |
Generated ChangeLog files are easy to spot in their $Header line, it |
13 |
contains "generated/ChangeLog", with the version of the generation |
14 |
script, the time of generation, and the name of the script that |
15 |
generated it. |
16 |
|
17 |
Because all ChangeLogs change because of the generation, all Manifests |
18 |
are re-generated as well. During this regeneration, they are signed |
19 |
with the Gentoo Prefix Portage Snapshot Signing Key (C6317B3C), which |
20 |
(as its name suggests) is also used for signing the portage tree |
21 |
snapshots. |
22 |
This means that as side-effect of generation of the ChangeLog files, the |
23 |
full tree is now signed, e.g. you can verify that the copy of the ebuild |
24 |
you have is the same as the one rsync0 had when creating the rsync tree. |
25 |
(And it doesn't mean much more than that.) |
26 |
|
27 |
Obvious advantage of ChangeLog generation for Prefix users is that |
28 |
packages which still live in our SVN Prefix "overlay", now have |
29 |
meaningful ChangeLogs with respect to commits made in the SVN tree, |
30 |
which often are fixes. See for example the Python ChangeLog[1]. |
31 |
|
32 |
ChangeLog generation should not change anything regarding ebuilds. If |
33 |
you see weird digest or manifest failures, please file a bug. |
34 |
|
35 |
|
36 |
[1] http://rsync1.prefix.freens.org/dev-lang/python/ChangeLog |
37 |
|
38 |
-- |
39 |
Fabian Groffen |
40 |
Gentoo on a different level |