From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: ChangeLog API Date: Thu, 24 Mar 2016 09:29:30 -0400 Message-ID: References: <56F2E619.30807@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1458826213 29901 80.91.229.3 (24 Mar 2016 13:30:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 24 Mar 2016 13:30:13 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 24 14:30:04 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aj5Kt-0004FH-Ll for ged-emacs-devel@m.gmane.org; Thu, 24 Mar 2016 14:30:03 +0100 Original-Received: from localhost ([::1]:50320 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aj5Kt-000146-0N for ged-emacs-devel@m.gmane.org; Thu, 24 Mar 2016 09:30:03 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35090) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aj5Kb-00013o-8z for emacs-devel@gnu.org; Thu, 24 Mar 2016 09:29:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aj5KV-0007dV-Lb for emacs-devel@gnu.org; Thu, 24 Mar 2016 09:29:45 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:48439) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aj5KV-0007dR-F3 for emacs-devel@gnu.org; Thu, 24 Mar 2016 09:29:39 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aj5KT-0003u4-Hb for emacs-devel@gnu.org; Thu, 24 Mar 2016 14:29:37 +0100 Original-Received: from 69-196-182-150.dsl.teksavvy.com ([69.196.182.150]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 24 Mar 2016 14:29:37 +0100 Original-Received: from monnier by 69-196-182-150.dsl.teksavvy.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 24 Mar 2016 14:29:37 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 24 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 69-196-182-150.dsl.teksavvy.com User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) Cancel-Lock: sha1:wCgHObXUnfRzjWM9Zxdzr+kRVrc= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:202168 Archived-At: >> Even if we had such an API, enforcing it as a requirement for a package's >> inclusion in GNU ELPA -- otherwise, most packages would probably ignore it -- >> would be rather heavy-weight. Further, the result would likely be a large >> volume of information for you to ingest. I don't see the cost/benefit ratio >> adding up for an API like this. > We already have a notion of per-file change logs, though: *GNU* ELPA packages include a ChangeLog that's auto-generated from the git log, and is hence at a 100% standardized place. So we could use that, to some extent. The problem is that this is ChangeLog, whereas what the end user would like to see, usually is a NEWS. Still, we could add to package.el some function to try and extract the ChangeLog from an installed package. And then compare the ChangeLog before upgrade to the ChangeLog after upgrade, to show the user what's actually changed. It would then be pretty easy to improve the code so that it uses a NEWS section in preference to the ChangeLog section, when available. Stefan