unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package xeft.el
Date: Mon, 16 Jan 2023 08:48:01 +0100	[thread overview]
Message-ID: <878ri2q5ep.fsf@web.de> (raw)
In-Reply-To: <E1pGvM1-0004wj-T9@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]


Richard Stallman <rms@gnu.org> writes:

>   > But the downside is also less than with shipping pure binaries, because
>   > platforms without shipped native-compiled code will just have a longer
>   > startup time, but the package will still work.
>
> Why do you expect this to affect startup time?  Are you assuming the
> first thing done after downloading the package will beto
> native-compile it?  Why should that be?

Usually a package is either native-compiled on first usage or directly
on installation. If it is not native-compiled on installation, the first
usage causes a compilation with the results saved into the eln-cache.

But I just realized that I had misunderstood the original suggestion:
it’s not actually compiled transparently, but needs to be compiled to be
usable at all.

I’m sorry for misunderstanding the extend of the compilation.

⇒ I was wrong and the policy should be held up.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

  reply	other threads:[~2023-01-16  7:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03  4:11 [ELPA] New package xeft.el Yuan Fu
2023-01-04  8:08 ` Jean Louis
2023-01-04 16:46   ` Fu Yuan
2023-01-06 17:34     ` Jean Louis
2023-01-10 10:48       ` Yuan Fu
2023-01-04 19:24 ` Stefan Monnier
2023-01-04 19:38   ` Karl Fogel
2023-01-06  5:48     ` Yuan Fu
2023-01-06  5:46   ` Yuan Fu
2023-01-06 16:21     ` Stefan Monnier
2023-01-10 10:57       ` Yuan Fu
2023-01-13  4:51         ` Richard Stallman
2023-01-13  9:54           ` Dr. Arne Babenhauserheide
2023-01-15  5:14             ` Richard Stallman
2023-01-16  7:48               ` Dr. Arne Babenhauserheide [this message]
2023-01-17  4:57                 ` Richard Stallman
2023-01-17 11:53                   ` Eli Zaretskii
2023-01-23  4:23                     ` Richard Stallman

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=878ri2q5ep.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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).