Am Donnerstag, 4. Februar 2016, 11:58:40 schrieb Yamaban:
On Thu, 4 Feb 2016 10:20, Axel Braun
wrote: 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.
Let me give you an example of a package that I just upgraded. I have added the changelog to the changes file, as this was requested earlier already: - hylafax 5.5.7 * fix ntries counter to apply to pages instead of documents (5 Dec 2015) * reject jobs rejected by the proxy (18-19 Nov 2015) * add RewriteFaxName and RewriteFaxNumber jobcontrol features (14 Nov 2015) * improve Chinese translation (7 Oct 2015) * make faxsetup fix blind references in Fontmap.HylaFAX (3 Oct 2015) * use the remote time on proxy job submisisons (17 Sep 2015) * create more-secure hosts.hfaxd passwords by default (28 Aug 2015) * add admin login feature for faxstat (27 Aug 2015) * add ProxyJobTag jobcontrol feature (26 Aug 2015) * fix grevious calculation problem with Class1RestrictPoorSenders and Class1RestrictPoorDestinations (20 Aug 2015) * add application/binary MIMEConverter (17 Jul 2015) * fix DynamicConfig for Class 1 modem data format support (15 Jul 2015) * fix crash in tagline imaging due to glyph ascent (23 Jun 2015) * stop messing with the FIFO during installs and uninstalls (16 Jun 2015) * avoid conflicts with a TTY environment variable (15 Jun 2015) * fix dataTimeout esp for modems with large buffers in non-ECM (22 May 2015) * fix dataTimeout primarily affecting 7200 bps ECM sending (15 May 2015) I do not feel this is interesting for an end user. Information about security fixes may be interesting, indeed. As in many thngs, you need to find the right balance.... Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org