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