On Thu, 4 Feb 2016 10:20, Axel Braun
Gesendet: Dienstag, 02. Februar 2016 um 12:16 Uhr Von: "Daniel Morris"
An: "Axel Braun" Cc: opensuse-packaging@opensuse.org, opensuse-factory@opensuse.org Betreff: Re: [opensuse-packaging] Re: [opensuse-factory] why there are so few packages in Factory, revisited 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.
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?
I feel so. An end user is not interested in the change log at all. A developer or packer may be interested, but mostly in case some things dont work. And in this case you have to dig deeper anyway....
I'd like to give some contra to Axel: I am very interested in having a competent changelog, esp. in view of long-term supported packages as seen in any Enterprise Linux and also Evergreen and we will see them in Leap. Notice of fixed bugs, foremost security (with reference to CVE or similar) is very helpful in checking whether or not a package is save enough to be in use, esp if you take public available servers. Details on new features/versions, details of solved bugs, etc should be in the %doc/Changelog, just the short and curlies in the .changes file. A short: Security fix for CVE [number], details in local Changelog, or see: [upstream-changelog-url] is enough in most most cases, other packages have no competent changelog them self, so more work is needed in the package changelog. Here the direct link to the upstream changelog is most helpful to inspect the happening without prior install of the package (or downloading the whole source). There we should think of exporting most of the package changelog into a file, e.g. %doc/Changelog.SUSE and just keeping a few last changes in full in the package changelog with a reference to this file. -- At best this should be automated, saving time and work for the packager (and reducing errors). - Yamaban. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org