unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: emacs-devel@gnu.org, monnier@IRO.UMontreal.CA, raman@google.com
Subject: Re: Auto-installing packages?
Date: Tue, 18 Sep 2018 23:40:28 -0400	[thread overview]
Message-ID: <E1g2TLo-0007Es-CQ@fencepost.gnu.org> (raw)
In-Reply-To: <87sh264w88.fsf@russet.org.uk> (phillip.lord@russet.org.uk)

[[[ 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. ]]]

In response to

  > >   > So, for the case of Emacs and ELPA installing over the network vs
  > >   > pre-packaged is, I think, merely technical.

I wrote this:

  > > That is a valid point, in the case of GNU ELPA.
  > >
  > > But would that facility be limited to GNU ELPA?

  > > Or would it also be used with other package archives
  > > that are not part of Emacs?

You responded

  > Emacs already has the ability to do this, but it is up to the user to
  > choose to do this.

That doesn't address the issue I am raising.  It is a tangent.

Emacs has the ability to do any computation at all, if a user programs
it.  The issue here is not what Emacs "has the ability to do", but
what it offers/encourages/suggests/makes convenient.

If we are going to add a convenient facility to load external
packages, it should be for ELPA (which is more or less a part of
Emacs), not for other package archives (which are NOT part of Emacs).

In general, treating all package archives alike is something to avoid.
It is a pitfall.

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2018-09-19  3:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14  1:51 Auto-installing packages? Stefan Monnier
2018-09-14  7:09 ` 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 [this message]
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=E1g2TLo-0007Es-CQ@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=phillip.lord@russet.org.uk \
    --cc=raman@google.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).