1 |
Il giorno mer, 01/06/2011 alle 18.59 -0400, Rich Freeman ha scritto: |
2 |
> Write up Changelogs for any change that impacts what gets installed on |
3 |
> our user's computers. |
4 |
> |
5 |
|
6 |
This is not really a good approach; Peter's approach is more reliable on |
7 |
this. |
8 |
|
9 |
Let me explain: an EAPI bump _should not_ impact what gets installed. On |
10 |
the other hand, I'd argue it _should_ be in the ChangeLog: |
11 |
|
12 |
a) it is a functional change: it changes _a lot_ the way the package |
13 |
manager sees the ebuild — even though one argues that if the package |
14 |
manager is perfectly compliant the result wouldn't change, it might very |
15 |
well expose a bug in the package manager; |
16 |
|
17 |
b) we can't assume nobody makes mistakes: "it's such a minimal change I |
18 |
cannot have made a mistake" is no way to argue a policy; mistakes are |
19 |
possible by anyone, and any change that is not strictly trivial |
20 |
(whitespace, comments) should be treated as a possible entrypoint for a |
21 |
mistake. |
22 |
|
23 |
-- |
24 |
Diego Elio Pettenò — Flameeyes |
25 |
http://blog.flameeyes.eu/ |