From: Glenn Morris <rgm@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 51234@debbugs.gnu.org, tk@giga.or.at
Subject: bug#51234: emacs.pdmp file name (--fingerprint)
Date: Mon, 18 Oct 2021 14:09:18 -0400 [thread overview]
Message-ID: <pqee8iw6gh.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87bl3mfnxu.fsf@igel.home> (Andreas Schwab's message of "Mon, 18 Oct 2021 15:43:41 +0200")
Andreas Schwab wrote:
> On Okt 18 2021, Eli Zaretskii wrote:
>
>> Me, I wonder how will those distros cope with the *.eln files, which
>> also include hashes that aren't known in advance.
>
> Packagers like RPM can cope with that by using wildcards. They can also
> generate file lists on the fly.
I feel like +1'ing this.
Plus they also warn if there are installed but unpackaged files, so
there isn't really a pressing need to announce/document the name change.
I see no need to add an option to revert to "emacs.pdmp".
>>> I've changed the package to rename the emacs-*.pdmp file to emacs.pdmp.
A mistake IMO.
prev parent reply other threads:[~2021-10-18 18:09 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
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 [this message]
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=pqee8iw6gh.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=51234@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=schwab@linux-m68k.org \
--cc=tk@giga.or.at \
/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.