[opensuse-packaging] Re: Re: 200 lines of changes?

On Wed, 7 Mar 2012 04:28, Claudio Freire wrote:

2012/3/7 Marguerite Su :

...

If it's there, I think no need to especially mention it, because every packager knows where to find it, while end users couldn't see your spec file at all.

End users do see the .changes file. You can see it with yast.

I check it regularly after updates, and only wish I could check *before* updating.

Maybe not inside yast, but if the .rpm is available (even via http://) them you can use "rpm --changelog -p " without installing the package first. I use rpm -p ... befor installing a new package that I do not know good enough to fly blind. Esp. the (soft) options : --suggests, --recommends, --enhances, --supplements are helpful, as only the hard options --requires, --obsoletes, --conflicts are visible inside yast. Maybe there is room for an enhancement in yast in this point? But overall, the most interesting info in .changes are: - why (upstream version, compiler-change, distro-specific-patch, error-patch, packager-mod-patch, etc) - when was the change (iso-date-time) - who has done the change. Everything else, e.g. the content of version-change should reside in %doc to keep .changes clear, non-confusing, and fast to read. A link (url) to upstream Changes-log, bugzilla entries, and such are welcome in my opinion. More or less it's a packager log. Who-has-when-done-what-and-why. Thats my 2ct. Critic is welcome, flames are not constructive. - Yamaban. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org