From: Thomas Klausner <tk@giga.or.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 51234@debbugs.gnu.org
Subject: bug#51234: emacs.pdmp file name (--fingerprint)
Date: Mon, 18 Oct 2021 14:33:53 +0200 [thread overview]
Message-ID: <20211018123353.pmegcy53lajqmb2w@yt.nih.at> (raw)
In-Reply-To: <83y26qecqd.fsf@gnu.org>
On Mon, Oct 18, 2021 at 03:31:06PM +0300, Eli Zaretskii wrote:
> Me, I wonder how will those distros code with the *.eln files, which
> also include hashes that aren't known in advance. Solving the issue
> with the pdumper file will still leave this other one, with many more
> files.
What are .eln files? I don't see any in the NetBSD build.
Here are the files for the emacs-git package.
https://github.com/NetBSD/pkgsrc-wip/tree/master/emacs-git
The PLIST contains the files that get installed, the Makefile and
options.mk contain any enable/disable arguments to configure.
> So perhaps the distros will just have to adapt?
I've changed the package to rename the emacs-*.pdmp file to emacs.pdmp.
Thomas
next prev parent reply other threads:[~2021-10-18 12:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 7:07 bug#51234: emacs.pdmp file name (--fingerprint) Thomas Klausner
2021-10-16 13:43 ` Lars Ingebrigtsen
2021-10-18 7:41 ` Lars Ingebrigtsen
2021-10-18 8:01 ` Robert Pluim
2021-10-18 8:04 ` Lars Ingebrigtsen
2021-10-18 8:26 ` Robert Pluim
2021-10-18 8:46 ` Lars Ingebrigtsen
2021-10-18 8:55 ` Robert Pluim
2021-10-18 13:13 ` Lars Ingebrigtsen
2021-10-18 14:16 ` Eli Zaretskii
2021-10-19 20:42 ` Lars Ingebrigtsen
2021-10-18 12:31 ` Eli Zaretskii
2021-10-18 12:33 ` Thomas Klausner [this message]
2021-10-18 12:50 ` Robert Pluim
2021-10-18 13:08 ` Eli Zaretskii
2021-10-18 12:31 ` Eli Zaretskii
2021-10-18 13:43 ` Andreas Schwab
2021-10-18 18:09 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211018123353.pmegcy53lajqmb2w@yt.nih.at \
--to=tk@giga.or.at \
--cc=51234@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.