Drew Adams wrote:
> If gnu-emacs-sources@gnu.org isn't deemed enough for some
> reason
Updates end up there automatically. The message you refer is
this:
From: ELPA update <do.not.re...@elpa.gnu.org>
Subject: [GNU ELPA] Csv-Mode version 1.23
To: gnu-emacs-sources@gnu.org
Cc: nil <emacs-de...@gnu.org>
Date: Mon, 15 Jan 2024 05:02:32 -0500 (10 weeks, 6 days ago)
I compared that to when my own ELPA package was released,
since that would have implied that it was announced on
emacs-devel, and it would have been interesting to hear if
anyone said anything. However, taking a closer look -
From: ELPA update <do.not.re...@elpa.gnu.org>
Subject: [GNU ELPA] Wrap-Search version 4.12.10
To: gnu-emacs-sources@gnu.org
Cc: Emanuel Berg <...>
Date: Mon, 02 Oct 2023 17:07:58 -0400 (25 weeks, 6 days ago)
- we see that this one wasn't CC'd to emacs-devel but to me.
So the automated posts to gnu-emacs-sources are CC to
the maintainer which is why it ended up on emacs-devel.
Package csv-mode is available.
Status: Available from gnu -- [Install]
Archive: gnu
Version: 1.23
Commit: 63f02980978f19786bda354457ac5259b8f969a2
Summary: Major mode for editing comma/char separated values
Requires: emacs-27.1, cl-lib-0.5
Website: https://elpa.gnu.org/packages/csv-mode.html
Keywords: [convenience]
Maintainer: <emacs-de...@gnu.org>
Author: Francis J. Wright <...>
> wouldn't info-gnu-em...@gnu.org be more appropriate?
ELPA packages are part of GNU Emacs, it says so in every .el
package:
This file is part of GNU Emacs.
So ELPA source is on-topic on emacs-devel. I think new ELPA
packages would very well be automatically announced there,
there are several advantages to that. But not individual
updates if that is what happened.
PS. Csv-Mode and Wrap-Search? Yuk! Why are package
names capitalized? Ugly! But it is also not how people use
them or how they appear in source.
PPS. GNU ELPA is refered to in three ways in this post.
The correct and formal GNU ELPA, the informal ELPA (by me
but also by the ELPA update gnu-emacs-sources poster),
and, by the package manager, like this
Archive: gnu
I guess it is because all our repositories are ELPAs, but it
still looks a bit comical to me. It is setup like that by
default in `package-archives'.
--
underground experts united
https://dataswamp.org/~incal
