From: Richard Stallman <rms@gnu.org>
To: Payas Relekar <relekarpayas@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] new package: tramp-docker
Date: Thu, 20 Oct 2022 15:45:58 -0400 [thread overview]
Message-ID: <E1olbUM-0008P4-S6@fencepost.gnu.org> (raw)
In-Reply-To: <87a65tsd2q.fsf@gmail.com> (message from Payas Relekar on Tue, 18 Oct 2022 14:41:52 +0530)
[[[ 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. ]]]
> While I am still in doubt whether it is possible to ensure a container
> can only be built using free software, similar to .deb packages, short
> of not using anything beyond official repos,
If that is the only reliable method, we should publicly say so.
First we should see what we can find.
> Partially agree. What we need to separate out is a mechanism to
> build/package/deploy (e.g. dpkg, containers) from mechanism to
> distribution (debian repos, docker repository).
In the abstract, I think your logic is correct.
Nonetheless, there seems to be a difference in practice between what
tends to happen when people release programs in other ways and when
people release them in containers. When developers release tarballs,
various users build them and may report, "Hay, this depends on the
nonfree library libdropdead." But when developers release containers,
users tend not to notice that one of the 50 packages included is
libdropdead and that that is nonfree.
This isn't the place to continue the discussion. I should move
it somewhere else. Would you like to be part of it?
--
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)
next prev parent reply other threads:[~2022-10-20 19:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 4:46 [ELPA] new package: tramp-docker Payas Relekar
2022-10-18 12:06 ` Richard Stallman
2022-10-18 9:11 ` Payas Relekar
2022-10-20 19:45 ` Richard Stallman [this message]
2022-10-21 11:35 ` Payas Relekar
[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-09-23 15:58 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-24 2:44 ` 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
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
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=E1olbUM-0008P4-S6@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=relekarpayas@gmail.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).