![](https://seccdn.libravatar.org/avatar/99278ec30f150a060043aaeca0ee5806.jpg?s=120&d=mm&r=g)
On 03/21/2013 11:49 AM, Richard Biener wrote:
On Thu, 21 Mar 2013, Togan Muftuoglu wrote:
Yes and no. If the changes affect the way the program behaves it should be included in the changes, but cosmetic things like fixing rpmlint errors or warnings (not mentioning the rpmlintrc file) that is cosmetic should not clutter the changes file.
Well, the .changes file is the _only_ place where changes in packaging can be documented. Changes in program behavior are documented in its own documentation, on web-pages in packaged README files, in the package description, etc.
So in the light of this view you are saying it is OK to say for changes of the software look at the README/website as there are not vital for the package to be upgraded/updated; but how the package it build is VERY imprortant and has to be documented. This not seeing the forest for the trees, this is red tape IMO Togan PS .please keep replies to the list only. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org