From: Gregory Heytings <gregory@heytings.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: svg library ideas
Date: Fri, 03 Feb 2023 00:19:52 +0000 [thread overview]
Message-ID: <b0bd26d378194c083f8f@heytings.org> (raw)
In-Reply-To: <87357oy7ar.fsf@yahoo.com>
>
> Building anything with Rust also involves downloading a lot of binary
> code off the internet, and I am not quite comfortable with that.
>
That sentence is guaranteed to make Richard raise an eyebrow, but it is
not correct.
When you build a Rust program, the build system does not download any
binary code at all: it downloads the _sources_ of all the dependencies of
the program, recursively, and everything is built from the sources.
(Note that all the sources are kept locally after building.)
It is when you build Emacs or any other program written in C or C++ that
you (usually) download a lot of binary code: you download the binary
packages of its dependencies that your distro provides.
next prev parent reply other threads:[~2023-02-03 0:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87lelo15vw.fsf.ref@yahoo.com>
2023-01-27 13:09 ` svg library ideas Po Lu
2023-01-27 16:36 ` Jean Louis
2023-01-29 5:18 ` Richard Stallman
2023-01-29 5:29 ` Po Lu
2023-01-29 6:44 ` Jim Porter
2023-01-29 6:51 ` Eli Zaretskii
2023-01-31 4:19 ` Richard Stallman
2023-01-31 5:16 ` Po Lu
2023-02-02 5:03 ` Richard Stallman
2023-02-02 5:18 ` Po Lu
2023-02-03 0:19 ` Gregory Heytings [this message]
2023-01-29 6:43 ` Eli Zaretskii
2023-02-03 6:39 Pedro Andres Aranda Gutierrez
2023-02-03 8:00 ` Eli Zaretskii
2023-02-03 11:25 ` Jean Louis
2023-02-03 12:31 ` Po Lu
2023-02-03 13:37 ` Jean Louis
2023-02-03 12:42 ` Eli Zaretskii
2023-02-03 13:56 ` Yuri Khan
2023-02-04 7:06 ` Jean Louis
2023-02-04 8:49 ` Eli Zaretskii
2023-02-04 18:38 ` Jean Louis
2023-02-05 4:29 ` Richard Stallman
2023-02-04 7:07 ` Jean Louis
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=b0bd26d378194c083f8f@heytings.org \
--to=gregory@heytings.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--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).