From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: acm@muc.de, Eli Zaretskii <eliz@gnu.org>, 74382@debbugs.gnu.org
Subject: bug#74382: `compile-first` Make rule is no longer using `load-prefer-newer`
Date: Mon, 18 Nov 2024 13:05:54 +0300 [thread overview]
Message-ID: <7b07de9fd995f14e3b4d675c7288108dbe57209c.camel@yandex.ru> (raw)
In-Reply-To: <m28qth1902.fsf@gmail.com>
On Mon, 2024-11-18 at 05:06 +0100, Gerd Möllmann wrote:
> Konstantin Kharlamov <Hi-Angel@yandex.ru> writes:
>
> > Even Gerd in this discussion forgot about this peculiarity — and
> > Gerd unlike me is a regular Emacs developer.
>
> Even worse, even worse: He wrote that stuff! But I think I'll excuse
> him
> because that was 25 years ago, and he took a 20 year break from
> Emacs,
> after stepping down, and he's old of course :-).
>
> Seriously, maybe knowing a bit of history helps understand the
> current
> situation wrt .elc files? One wouldn't believe it nowadays, but they
> were originally in version control, i.e. RCS, and later CVS. I didn't
> want that in the public CVS repo we set up for Emacs 21, so I added
> the
> ability to bootstrap and removed the .elc files from CVS.
> COMPILE_FIRST
> and so on are part of the bootstrapping support.
Btw, thank you, this bit of history indeed is interesting. During whole
discussion I had a question on the back of my mind: how this
"distribute pre-built elc in tarballs" idea initially came to be. I
mean, it's kind of nice from POV of saving a bit of energy around the
world on CI machines, but I don't see much beyond that. Building elc
files is not *that* bad for elc distribution to be strictly necessary.
Now that you told this, I realize it's just a solution to a problem
from 25 years old back, from times when that actually was a problem.
next prev parent reply other threads:[~2024-11-18 10:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 15:11 bug#74382: `compile-first` Make rule is no longer using `load-prefer-newer` Konstantin Kharlamov
2024-11-16 16:27 ` Eli Zaretskii
2024-11-16 16:53 ` Alan Mackenzie
2024-11-16 17:45 ` Konstantin Kharlamov
2024-11-16 18:38 ` Eli Zaretskii
2024-11-16 18:43 ` Konstantin Kharlamov
2024-11-16 20:00 ` Eli Zaretskii
2024-11-16 22:54 ` Konstantin Kharlamov
2024-11-17 6:44 ` Eli Zaretskii
2024-11-17 15:31 ` Konstantin Kharlamov
2024-11-17 7:25 ` Gerd Möllmann
2024-11-17 15:21 ` Konstantin Kharlamov
2024-11-17 15:37 ` Eli Zaretskii
2024-11-17 15:43 ` Konstantin Kharlamov
2024-11-17 15:53 ` Eli Zaretskii
2024-11-17 16:04 ` Konstantin Kharlamov
2024-11-17 16:29 ` Eli Zaretskii
2024-11-17 16:46 ` Konstantin Kharlamov
2024-11-17 17:09 ` Eli Zaretskii
2024-11-17 17:24 ` Konstantin Kharlamov
2024-11-18 4:06 ` Gerd Möllmann
2024-11-18 6:19 ` Konstantin Kharlamov
2024-11-18 10:05 ` Konstantin Kharlamov [this message]
2024-11-18 12:59 ` Eli Zaretskii
2024-11-18 13:12 ` Konstantin Kharlamov
2024-11-18 13:38 ` Eli Zaretskii
2024-11-17 15:43 ` Gerd Möllmann
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=7b07de9fd995f14e3b4d675c7288108dbe57209c.camel@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=74382@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
/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).