Re: [nongnu] main 385623dca6 2/2: * elpa-packages (notmuch): New package.

[David Bremner <david@tethera.net>]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> I know that you don't want to commit notmuch-pkg.el to git, and that's
>> in fact undesirable from a NonGNU ELPA point of view, it turns out.  But
>> given how there is already version.txt and version.py, could we have a
>> header in notmuch.el too, do you think?
>
> BTW, in an ideal world (from the perspective of NonGNU ELPA as well as
> that of those Emacs users who install the Notmuch ELisp package via
> things like Borg, Straight, or `package-vc`, but install the rest of
> Notmuch some other way (e.g. from their GNU/Linux distribution)) the
> `emacs` subdirectory would be split into its own branch or repository.

This is not likely to happen any time soon. The emacs front-end is
developed (and tested) in tandem with the C/C++ backend and the
sphinx-doc based documentation.

Running the latest emacs front-end against an arbitrarily old version of
the notmuch binaries has never been supported, hence the following
commentary in notmuch.el.

;; Note for MELPA users (and others tracking the development version
;; of notmuch-emacs):
;;
;; This emacs package needs a fairly closely matched version of the
;; notmuch program. If you use the MELPA version of notmuch.el (as
;; opposed to MELPA stable), you should be prepared to track the
;; master development branch (i.e. build from git) for the notmuch
;; program as well. Upgrading notmuch-emacs too far beyond the notmuch
;; program can CAUSE YOUR EMAIL TO STOP WORKING.
;;
;; TL;DR: notmuch-emacs from MELPA and notmuch from distro packages is
;; NOT SUPPORTED.

Of course it's free software, and people can do what they like, but it
does give some idea of where we going to focus our limited resources.