all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] new package: tramp-docker
Date: Sat, 08 Oct 2022 18:34:06 -0400	[thread overview]
Message-ID: <E1ohIOU-0007lO-75@fencepost.gnu.org> (raw)
In-Reply-To: <871qrkkrvv.fsf@posteo.net> (message from Philip Kaludercic on Fri, 07 Oct 2022 07:35:48 +0000)

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

  > > 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?

  > Yes, both are free software.

That is a relief -- at the first level, this is not a problem.

  > To my knowledge there is the danger of either having a build-time or a
  > run-time dependency on a non-free container,

That's what was reported to me.

Does Docker provide an easy way to verify that you have avoided such
dependencies?  A way to make sure to avoid including them?

                                                 though looking through a
  > container index like (https://hub.docker.com/search?q=)

I tried visiting http://hub.docker.com/ and got a blank window.  It depends
on nonfree software to see even the first page.  We must not refer anyone
to that site.

Likewise for https://hub.docker.com/search.

I surmise that the standard way to develop a container involves using
https://hub.docker.com/search.  Is that correct?

Is that the _only_ way to develop a container?  Is it possible,
practically speaking, to build a container without using that site at all?

Has anyone here had practical experience?

                                                           , it appears that
  > the overwhelming majority of popular software is free software, if only
  > because distribution is easier.

Alas, that does not by itself ensure that, supposing you build a container,
you won't consider including nonfree programs.

Is there an easy way you can ensure that _all_ the programs you put
into a new container are free?  Is there an easy way to verify that
the contents of a container are free?

After I get a little information here, I will ask on gnu-misc-discuss.

  > That being said, TRAMP+Docker is a popular combination for developing
  > software, so what people often just do is use a distribution image
  > (Ubuntu, Debian, Alpine) as the foundation and then instruct the
  > container to install all the software they need using the distributions
  > package manager, while building their own image.

I see how that is buzarre, but paradoxically it might work in
freedom's favor here.  If you use a free distro to build the
container, and put things in it with apt-get, you will get only free
software in it.  Maybe that is a reliable method we could recommend.

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

  > I think this could be added to the commentary section.

Maybe so, but when you say "the commentary section", could you
be more precise?  The commentary section of what documentation?


After I get a little information here, I will move this to gnu-misc-discuss.

-- 
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)





  reply	other threads:[~2022-10-08 22:34 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
2022-10-07  7:35       ` Philip Kaludercic
2022-10-08 22:34         ` Richard Stallman [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1ohIOU-0007lO-75@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.