unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: shipping elisp for notmuch in elpa-notmuch debian package
Date: Wed, 04 Dec 2019 08:53:14 -0400	[thread overview]
Message-ID: <87muc8qmkl.fsf@tethera.net> (raw)
In-Reply-To: <87a7887akl.fsf@fifthhorseman.net>

Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

> Hi Notmuch folks--
>
> In the course of trying to figure out the dh_missing warnings, I've been
> looking into what we ship in debian in the elpa-notmuch package.
>
> Dubious files
> -------------
>
> elpa-notmuch currently ships a few files in
> /usr/share/emacs/site-lisp/elpa-src/notmuch-*/ that i'm not convinced we
> actually want to ship in the distributed package.
>
> Those are:
>
>     rstdoc.el
>     make-deps.el
>     dir

the first two are build tools. The latter is needed by the info files.

>
> Do we need any of the above in the elpa-notmuch package?
>
> info files
> ----------
>
> The package also ships a bunch of *.info files in that elpa
> module-specific directory, rather than shipping them in the typical
> /usr/share/info/ location.  These info files appear to be translations
> of the manpages or other basic notmuch documentation.  Is there a reason
> to ship them in the elpa-specific directory?
>

It makes the elpa (make elpa) package self contained (with docs).
package.el knows how to install info files, so the debian-specific
tooling is not needed.

> notmuch-pkg.el
> --------------
>
> I note that notmuch-pkg.el is installed in elpa-notmuch, but it is *not*
> in /usr/share/emacs/site-lisp when installed via the standard "make
> install".  i don't know enough about how that installation is supposed
> to work, but if it's supposed to drop in a notmuch-pkg.el, then
> something needs fixing in the baseline "make install".

It's metadata for the elpa (package.el) package. Not sure it is helpful
in the standard install, but I don't really use the standard install, so
I'm open to ideas

  reply	other threads:[~2019-12-04 12:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04  8:35 shipping elisp for notmuch in elpa-notmuch debian package Daniel Kahn Gillmor
2019-12-04 12:53 ` David Bremner [this message]
2019-12-04 15:15   ` Daniel Kahn Gillmor
2019-12-04 19:29     ` David Bremner
2019-12-06 21:20       ` Daniel Kahn Gillmor
2019-12-07 14:32         ` David Bremner
2019-12-09 18:09           ` Daniel Kahn Gillmor

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=87muc8qmkl.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=dkg@fifthhorseman.net \
    --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).