unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Robin Tarsiger <rtt@dasyatidae.com>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] new package: tramp-docker
Date: Thu, 06 Oct 2022 18:03:58 -0400	[thread overview]
Message-ID: <E1ogYyE-0001fZ-H5@fencepost.gnu.org> (raw)
In-Reply-To: <d83a592d-30a7-feb7-92b5-5b84561f7e6a@dasyatidae.com> (message from Robin Tarsiger on Sat, 24 Sep 2022 00:53:21 -0500)

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

  > This code is used to access files in Docker or Podman containers that are
  > running on the same system as Emacs. It calls the Docker or Podman program
  > to spawn a shell inside the container to communicate with. It is similar
  > to the su or sudo Tramp methods, in that the connection to the "remote"
  > system involves shared kernel resources (unless Docker or Podman itself
  > eventually chooses to do something else).

Thanks for explaining.  My overload is such that I just saw this today
-- because I recalled I hadn't seen a reply and decided to search for it.

Now I understand what this is does, and it will be a convenient
feature.  But it raises a couple of possible moral issues.

1. Is the Docker program free software?  Is the Podman program free
software?  If neither of them is free software, is this a feature that
promotes running nonfree software on GNU?

2. Supposing that one of them is free software, and there is no
problem of that kind, there's another problem that people have
reported to me: in making a container, there is a risk of including
nonfree programs and you can't easily tell if that has happened, let
alone make sure it won't happen.  The container-making process tends
to pull in dependencies without checking whether they are free.

That is not a reason to refuse to support this access-into-containers
feature, but we should take advantage of this feature and its
documentation to inform people about that problem.

3. Distributing free programs in containers tends to be bad for
the community's control over the program.  Because people
don't build the program on the GNU/Linux distros they use,
and don't package it for those distros.

This too we should use the opportunity to warn people about.


-- 
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-10-06 22:03 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 15:58 [ELPA] new package: tramp-docker Brian Cully via Emacs development discussions.
2022-09-23 16:19 ` Philip Kaludercic
2022-09-23 17:47 ` Michael Albinus
     [not found]   ` <63d5f29a-05ed-f8c5-796c-a6eb9e28d575@spork.org>
2022-09-23 18:00     ` Michael Albinus
2022-09-23 18:09       ` Michael Albinus
2022-09-24 10:34         ` Michael Albinus
     [not found]           ` <44bd6537-316c-acc7-a4d6-6123bc32e2c0@spork.org>
2022-09-24 16:56             ` Michael Albinus
2022-09-24 17:31               ` Brian Cully via Emacs development discussions.
2022-09-27 16:54                 ` Michael Albinus
2022-09-24  2:44 ` [ELPA] " Richard Stallman
2022-09-24  5:53   ` Robin Tarsiger
2022-09-24 10:45     ` Michael Albinus
2022-10-06 22:03     ` Richard Stallman [this message]
2022-10-07  7:35       ` Philip Kaludercic
2022-10-08 22:34         ` Richard Stallman
2022-10-09 11:54           ` Philip Kaludercic
2022-10-15 20:43             ` Richard Stallman
2022-10-15 20:43             ` Richard Stallman
2022-10-16 13:33               ` Philip Kaludercic
2022-10-17 12:30               ` zimoun
2022-10-19 17:02                 ` Richard Stallman
2022-10-20  8:18                   ` zimoun
2022-10-22 20:03                     ` Richard Stallman
2022-10-15 20:43             ` Richard Stallman
2022-10-10 13:55           ` Brian Cully via Emacs development discussions.
2022-10-10 17:46           ` zimoun
2022-10-03 13:03 ` Philippe Vaucher
     [not found] <bf072225-5933-aef0-6fed-4da031311766@spork.org>
2022-10-03 13:45 ` Brian Cully via Emacs development discussions.
2022-10-03 17:52   ` Michael Albinus
  -- strict thread matches above, loose matches on Subject: below --
2022-10-16  4:46 Payas Relekar
2022-10-18 12:06 ` Richard Stallman
2022-10-18  9:11   ` Payas Relekar
2022-10-20 19:45     ` Richard Stallman
2022-10-21 11:35       ` Payas Relekar

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=E1ogYyE-0001fZ-H5@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rtt@dasyatidae.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).