unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: yoni@rabkins.net, emacs-devel@gnu.org
Subject: Re: Adding Emms to ELPA (take 2), and a technical question
Date: Wed, 29 Apr 2020 10:13:41 +0200	[thread overview]
Message-ID: <m2sggmwvyi.fsf@gmail.com> (raw)
In-Reply-To: <E1jTdJH-0006I9-6x@fencepost.gnu.org> (Richard Stallman's message of "Tue, 28 Apr 2020 23:22:55 -0400")

>>>>> On Tue, 28 Apr 2020 23:22:55 -0400, Richard Stallman <rms@gnu.org> said:

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

    >> Iʼd take a look at 'pdf-tools', it both compiles C-code and installs
    >> necessary packages using 'apt-get' and similar.

    Richard> That is an undesirable practice: it turns package installation into
    Richard> something users won't keep track of.

If you want to use pdf-tools, and decide not to let it install the
required packages for you, you have to install them on its behalf. I
donʼt see the practical difference. The documentation of pdf-tools is
very clear about how to do the installation by hand.

    Richard> (Secondary practical issue: to succeed in running apt-get it would
    Richard> have to run as root, I think.)

It uses 'sudo', and is very clear about that too. Of course if youʼre
installing by hand you can install packages as non-root and play games
with PKG_CONFIG_PATH to get pdf-tools to find them.

(this is where someone points out a GNU/Linux package management
system where *everything* is installed as non-root :-) )

Robert



  reply	other threads:[~2020-04-29  8:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 19:06 Adding Emms to ELPA (take 2), and a technical question Yoni Rabkin
2020-04-25  3:25 ` Stefan Monnier
2020-04-28 13:28   ` Yoni Rabkin
2020-04-28 15:06     ` Robert Pluim
2020-04-28 16:02       ` Yoni Rabkin
2020-04-29  3:22       ` Richard Stallman
2020-04-29  8:13         ` Robert Pluim [this message]
2020-04-30  2:32           ` Richard Stallman
2020-04-29 11:53         ` Yoni Rabkin
2020-04-30 14:43         ` Yoni Rabkin
2020-05-01  2:52           ` Richard Stallman
2020-05-01  6:32             ` Joost Kremers
2020-05-01 14:07               ` Arthur Miller
2020-05-01 14:42                 ` Joost Kremers
2020-05-01 14:51                   ` Arthur Miller
2020-04-29 10:07       ` Basil L. Contovounesios
2020-04-29 12:45         ` Stefan Monnier
2020-05-27 19:44   ` Yoni Rabkin
2020-05-28  2:36     ` Stefan Monnier
2020-05-28  5:34       ` Sean Whitton
2020-05-29  2:46       ` Yoni Rabkin
2020-06-15 19:32 ` Yoni Rabkin

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=m2sggmwvyi.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=yoni@rabkins.net \
    /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).