From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: Changelog message for updating packages Date: Sun, 8 Nov 2020 13:31:30 +0300 Message-ID: References: <20201108100646.vaynfw4fhdiff27m@E15-2016.optimum.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2734"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/+ (1036f0e) (2020-10-18) Cc: Emacs-Devel List To: Boruch Baum Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Nov 08 14:42:06 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kbkxJ-0000cx-EP for ged-emacs-devel@m.gmane-mx.org; Sun, 08 Nov 2020 14:42:05 +0100 Original-Received: from localhost ([::1]:37368 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kbkxI-0006H5-G0 for ged-emacs-devel@m.gmane-mx.org; Sun, 08 Nov 2020 08:42:04 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43542) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kbkvN-0004wt-FD for emacs-devel@gnu.org; Sun, 08 Nov 2020 08:40:05 -0500 Original-Received: from static.rcdrun.com ([95.85.24.50]:39201) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kbkvJ-0005L5-QY for emacs-devel@gnu.org; Sun, 08 Nov 2020 08:40:04 -0500 Original-Received: from localhost ([::ffff:197.157.34.177]) (AUTH: PLAIN admin, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by static.rcdrun.com with ESMTPSA id 00000000002C0004.000000005FA7F528.00003718; Sun, 08 Nov 2020 13:39:51 +0000 Content-Disposition: inline In-Reply-To: <20201108100646.vaynfw4fhdiff27m@E15-2016.optimum.net> Received-SPF: pass client-ip=95.85.24.50; envelope-from=bugs@gnu.support; helo=static.rcdrun.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/11/08 08:39:38 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] X-Spam_score_int: -2 X-Spam_score: -0.3 X-Spam_bar: / X-Spam_report: (-0.3 / 5.0 requ) BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:258895 Archived-At: * Boruch Baum [2020-11-08 13:08]: > As an emacs user, I would like to know before updating a package what is > in store for me if I decide to perform an update. As a programmer, I > would like to inform / warn users of changes or new features when they > update. This has become a standard feature of linux package managers and > ought to become a feature of emacs' package.el IMO. For example, in > debian one can perform 'apt changelog foo' prior to upgrading package > foo, and a developer can prepare an update message that appears after an > upgrade (and is also mailed to the admin's mailbox). You may find it in Emacs Lisp manual under (elisp) Packaging D.8 Conventional Headers for Emacs Libraries ============================================ ‘;;; Change Log:’ This begins an optional log of changes to the file over time. Don’t put too much information in this section—it is better to keep the detailed logs in a version control system (as Emacs does) or in a separate ‘ChangeLog’ file. ‘History’ is an alternative to ‘Change Log’. > Participating packages would need to have some standardized changelog > file and possible message file, and package.el would need one extra > interactive function and a handler for the possible messages. Explore those many ready functions. I am using some of them. add-change-log-entry add-change-log-entry-other-window add-log--changelog-buffer-p add-log--pseudo-changelog-buffer-name add-log-find-changelog-buffer change-log-beginning-of-defun change-log-end-of-defun change-log-fill-forward-paragraph change-log-fill-parenthesized-list change-log-find-file change-log-get-method-definition change-log-get-method-definition-1 change-log-goto-source change-log-goto-source-1 change-log-goto-source-internal change-log-indent change-log-insert-entries change-log-merge change-log-mode change-log-name change-log-next-buffer change-log-next-error change-log-read-defuns change-log-read-entries change-log-resolve-conflict change-log-search-file-name change-log-search-tag-name change-log-search-tag-name-1 change-log-sortable-date-at change-log-version-number-search diff-add-change-log-entries-other-window find-change-log log-edit-add-to-changelog log-edit-changelog--pattern log-edit-changelog-entries log-edit-changelog-entry log-edit-changelog-insert-entries log-edit-changelog-ours-p log-edit-changelog-paragraph log-edit-changelog-subparagraph log-edit-comment-to-change-log log-edit-generate-changelog-from-diff log-edit-insert-changelog log-edit-insert-changelog-entries log-edit-insert-filenames-without-changelog log-edit-narrow-changelog prompt-for-change-log-name smart-lisp-at-change-log-tag-p vc-cvs-update-changelog vc-rcs-update-changelog vc-update-change-log