unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: casouri@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: How to distribute dynamic modules by themselves?
Date: Wed, 23 Mar 2022 23:19:30 -0400	[thread overview]
Message-ID: <E1nXE0Y-0000by-CQ@fencepost.gnu.org> (raw)
In-Reply-To: <87y210apam.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed,  23 Mar 2022 12:20:17 +0100)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > I'm not quite sure what the state of dynamic modules on ELPA is.
  > Stefan?

One issue is, what do you need to do to make it possble to run that
dynamic module.  There may be security issues, too.  Do we know
an expert to consult about that?
-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





      parent reply	other threads:[~2022-03-24  3:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-20 23:51 How to distribute dynamic modules by themselves? Yuan Fu
2022-03-21  1:31 ` Zhu Zihao
2022-03-22  5:07 ` Richard Stallman
2022-03-22  8:44   ` Zhu Zihao
2022-03-23  3:55     ` Richard Stallman
2022-03-23 19:44       ` Yuan Fu
2022-03-25  3:29         ` Richard Stallman
2022-03-23 11:20 ` Lars Ingebrigtsen
2022-03-23 19:48   ` Yuan Fu
2022-03-25  3:29     ` Richard Stallman
2022-03-25  5:53       ` Yuan Fu
2022-03-27  5:27         ` Richard Stallman
2022-03-27  5:27         ` Richard Stallman
2022-03-23 22:16   ` Stefan Monnier
2022-03-23 22:30     ` Ergus
2022-03-24  3:19   ` Richard Stallman [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

  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=E1nXE0Y-0000by-CQ@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).