Best practices wrt. Changelog entries in spec file (upstream vs. specfile)

[Jason L Tibbitts III]

>>>>> "MS" == Michael Schwendt <bugs.michael at gmx.net> writes:

MS> A fearful user downloads new packages and performs a test upgrade
MS> on a test machine.

So, I guess I misunderstood what you meant when you said that you
could look into rpms to read included documentation.  It seems there
isn't any such way, which is a shame.  Obviously we can't assume that
everyone who cares to just read the README before upgrading will have
an extra system hanging around.  It should be quite possible to script
around yumdownloader with a call to rpm2cpio and a subshell exec.
Maybe if I can find some time.

MS> This belongs into the "spec %changelog should [...] cover
MS> important changes in the packaging" as an incompatible version
MS> upgrade means that you need to put a warning into your %changelog
MS> because _you created_ an _incompatible package_.

All of the underling would seem to suggest otherwise, but from my end
it really looks like you're agreeing with me here, which I certainly
can't complain about.

 - J<