Daniel Morris wrote:
On Tue, Feb 02, 2016 at 08:29:15AM +0100, Axel Braun wrote:
Am Dienstag, 2. Februar 2016, 08:25:20 schrieb Michael Ströder:
Personally two things annoying me: 1. Some reviewers insist on adding a lot of lines to .changes files claiming that there are common practices to do so. But many packages do this differently. And personally I think it's plain wrong to add all upstream changes to fit into .changes when simply updating to a new upstream release.
+1 if someone is really interested in details, reading the changelog upstream should be sufficient.
-1 That requires a user to download the upstream package independently just because the packaging process has intentionally truncated or abridged the information - "updated from upstream" is about as useful as the "fixed some bugs" message popular on some mobile appstores.
It's not a big deal for a package foo to add the upstream changes file in /usr/share/doc/packages/foo
Or am I misunderstanding how an end-user is supposed to inspect/query what has changed in a pre-built package using the tools provided by the package manager?
Could you please elaborate on what's an "end-user"? Ciao, Michael.