From: Dima Kogan <dima@secretsauce.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Gregory Heytings <gregory@heytings.org>,
48342@debbugs.gnu.org, akrl@sdf.org
Subject: bug#48342: native-comp emacs gets into an infinite loop at startup if no .el files are available
Date: Tue, 11 May 2021 12:59:27 -0700 [thread overview]
Message-ID: <87lf8lyrc0.fsf@secretsauce.net> (raw)
In-Reply-To: <83eeed3v78.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> Imagine the plight of a user who needs to discover all these places
> just to have the sources available.
I suppose you have a point, but this concern is much bigger than just
emacs. A user of a binary distro (pretty much all of them) may have a
binary package installed (anything; not just emacs), and could go
looking for sources many decades later. These are available, but will
take some work to find if you wait that long. Fixing this is a large
battle, and I'm not convinced it's worth fighting.
For Debian specifically, the snapshot.debian.org repos Gregory mentioned
are primarily useful to people that use the unstable packages. The
official, released, packages live in more standard locations, and should
be easier to get, even decades later. I say "should" because this is not
a common need, and I never went looking myself.
next prev parent reply other threads:[~2021-05-11 19:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 7:47 bug#48342: native-comp emacs gets into an infinite loop at startup if no .el files are available Dima Kogan
2021-05-11 8:37 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-11 8:44 ` Dima Kogan
2021-05-11 12:33 ` Eli Zaretskii
2021-05-11 17:00 ` Gregory Heytings
2021-05-11 17:12 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-11 17:29 ` Dima Kogan
2021-05-11 17:43 ` Eli Zaretskii
2021-05-11 17:57 ` Dima Kogan
2021-05-11 18:57 ` Gregory Heytings
2021-05-11 19:11 ` Eli Zaretskii
2021-05-11 19:38 ` Gregory Heytings
2021-05-11 19:51 ` Eli Zaretskii
2021-05-11 19:59 ` Dima Kogan [this message]
2021-05-11 20:23 ` Eli Zaretskii
2021-05-11 20:00 ` Gregory Heytings
2021-05-11 20:04 ` Gregory Heytings
2021-05-11 17:45 ` Eli Zaretskii
2021-05-11 19:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-02 16:44 ` Lars Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lf8lyrc0.fsf@secretsauce.net \
--to=dima@secretsauce.net \
--cc=48342@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=gregory@heytings.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://git.savannah.gnu.org/cgit/emacs.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).