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 15:29:24 -0400 [thread overview]
Message-ID: <87eexjrisr.fsf@tethera.net> (raw)
In-Reply-To: <877e3c6s0o.fsf@fifthhorseman.net>
Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
> On Wed 2019-12-04 08:53:14 -0400, David Bremner wrote:
>> Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
>>> rstdoc.el
>>> make-deps.el
>>> dir
>>
>> the first two are build tools.
>
> if they're build tools then we don't need to ship them with
> elpa-notmuch, right?
Correct.
>
>> The latter is needed by the info files.
>
> needed how? what functionality is missing? with the current
> elpa-notmuch installed, if i do "M-x info" i see a bunch of notmuch
> entries that show up under a big "Miscellaneous" heading, which appears
> to be the contents of this /dir file. If the purpose of it is just
> filing it under "Miscellaneous" that doesn't seem like much of a filing
> operation :P
iirc, it's needed to have them show up at all. Quite possibly the
contents of 'dir' could be improved.
>>> 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.
>
> sure, but if i "info notmuch" right now in debian, even with
> elpa-notmuch installed, i just get info redisplaying the notmuch(1)
> manpage, rather than rendering the info file which exists. Is that the
> goal?
no. the standalone info reader is a weakness of this approach, since it
only looks in /usr/share/info.
It depends who you care about more, non-debian users of the elpa
package, or users of the standalone info reader. I'm not either...
next prev parent reply other threads:[~2019-12-04 19:29 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
2019-12-04 15:15 ` Daniel Kahn Gillmor
2019-12-04 19:29 ` David Bremner [this message]
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=87eexjrisr.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).