unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: notmuch@notmuchmail.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: [nongnu] main 385623dca6 2/2: * elpa-packages (notmuch): New package.
Date: Tue, 20 Dec 2022 16:39:33 -0700	[thread overview]
Message-ID: <871qot1w7e.fsf@melete.silentflame.com> (raw)
In-Reply-To: <jwvv8m551h4.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 20 Dec 2022 14:44:46 -0500")

Hello notmuch maintainers,

As discussed on IRC, I'm seeing if I can add notmuch.el to NonGNU ELPA.

Currently the build is failing and Stefan Monnier, who designed the
packaging scripts, suggests adding a Version: header to notmuch.el:

On Tue 20 Dec 2022 at 02:44PM -05, Stefan Monnier wrote:

>> +  :make ("emacs/notmuch-pkg.el" "emacs/notmuch-version.el")
>
> (Non)GNU ELPA really wants to create the <foo>-pkg.el from the headers
> in the <foo>.el main file.  The above may sometimes work but will bite
> us sooner or later.
>
>> +  ;; FIXME: notmuch-pkg.el is not committed to Git.
>
> Please don't fix this.  If it's in the Git it gets worse (tends to
> create spurious conflicts while building the package.  Our scripts
> *should* be resilient to such problems, but based on past experience,
> I doubt they are yet in all cases).
> [...]
> The fix should start by adding a `Version:` to the `notmuch.el` file.
> [...]
> But in any case, a `grep 0.37` in the repository shows that they already
> have two copies of the version number (one in `version.txt` and one in
> `bindings/python/notmuch/version.py`), so adding a third shouldn't
> be a big deal.

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?

Thanks.

-- 
Sean Whitton

       reply	other threads:[~2022-12-20 23:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <167139941586.12438.1105626110857907494@vcs2.savannah.gnu.org>
     [not found] ` <20221218213656.56E0AC0061B@vcs2.savannah.gnu.org>
     [not found]   ` <jwvv8m551h4.fsf-monnier+emacs@gnu.org>
2022-12-20 23:39     ` Sean Whitton [this message]
2022-12-21  5:07       ` [nongnu] main 385623dca6 2/2: * elpa-packages (notmuch): New package Stefan Monnier
2022-12-21 12:30         ` David Bremner
2022-12-21 11:53       ` David Bremner
2022-12-22 20:54         ` Sean Whitton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871qot1w7e.fsf@melete.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).