unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: rms@gnu.org
Cc: philipk@posteo.net, emacs-devel@gnu.org
Subject: Re: [ELPA] new package: tramp-docker
Date: Thu, 20 Oct 2022 10:18:13 +0200	[thread overview]
Message-ID: <87o7u6kiwq.fsf@gmail.com> (raw)
In-Reply-To: <E1olCSf-0000Jv-Gc@fencepost.gnu.org>

Hi,

On mer., 19 oct. 2022 at 13:02, Richard Stallman <rms@gnu.org> wrote:

>   >   Alas, the natural consequence is that
>   > > building containers implies a risk of including nonfree software.  The
>   > > more packages, the more risk.
>
>   > > As long as that is the case, we should warn people off of distributing
>   > > containers.
>
>   > Container is not the issue – it is just a format for packing as tar is.
>
> That is true, in a sense, but it is only one abstract part of the truth.
> I stand by what I said.
>
>   > GNU Guix produces container images including only free software and not
>   > relying on Docker binary or infrastructure.
>
> That is good -- as far as it goes.  But most people who build
> containers to release a free program don't do it with GNU Guix.  And I
> don't think most of them are free software activists.  When they
> release free program this way, the risk is real.

Applying this logic and argument, you have to put the same
consideration and/or warning around the usage of GNU tar inside GNU
Emacs.  Because your concern applies equally.

Which additional criteria do you apply for “container“ that you do not
apply for the usage of GNU tar inside GNU Emacs?


Cheers,
simon





  reply	other threads:[~2022-10-20  8:18 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
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 [this message]
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=87o7u6kiwq.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=rms@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).