unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: emacs-devel@gnu.org
Subject: Auto-installing packages?
Date: Thu, 13 Sep 2018 21:51:09 -0400	[thread overview]
Message-ID: <jwvbm90hnbo.fsf-monnier+emacs@gnu.org> (raw)


Every time I see someone asking for or posting a little Elisp snippet
that automatically installs packages at Emacs startup, I'm wondering how
to answer that need: OT1H I find such requests fundamentally flawed in
terms of security, privacy, and reliability, but OTOH they correspond to
a real desire and lots of our users seem to not only be willing to
forego their security, privacy and reliability for that feature, but
they actually do so.

So, I'm wondering how we could better serve our users by providing them
with an alternative solution to their underlying need, which hopefully
suffers less from those problems.

Maybe some way to have something along the line of autoloads but that
instead of loading the Elisp code from a locally installed package, they
prompt the user explaining that this functionality requires installing
package FOO, etc?


        Stefan



             reply	other threads:[~2018-09-14  1:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14  1:51 Stefan Monnier [this message]
2018-09-14  7:09 ` Auto-installing packages? Phil Sainty
2018-09-14  8:39 ` T.V Raman
2018-09-15  0:46   ` Richard Stallman
2018-09-17 11:50     ` Phillip Lord
2018-09-17 22:51       ` Richard Stallman
2018-09-18 16:16         ` Phillip Lord
2018-09-19  3:40           ` Richard Stallman
2018-09-20 16:58             ` Phillip Lord
2018-09-24  1:46               ` Richard Stallman
2018-09-14 14:11 ` Phillip Lord
2018-09-14 18:17   ` Stefan Monnier
2018-09-17 11:48     ` Phillip Lord
2018-09-17 13:40       ` Stefan Monnier
2018-09-18 16:12         ` Phillip Lord
2018-09-18 21:05           ` Stefan Monnier
2018-09-14 15:52 ` Perry E. Metzger
2018-09-15  0:50   ` 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=jwvbm90hnbo.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@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).