From: "Joonas Sarajärvi" <muep@iki.fi>
To: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Any interest in making Emacs available on Flathub?
Date: Fri, 20 Apr 2018 21:39:09 +0300 [thread overview]
Message-ID: <5b48cd55-429a-9a50-ad13-eaf0ac9a074b@iki.fi> (raw)
In-Reply-To: <E1f9N6k-0007XY-Fa@fencepost.gnu.org>
Richard Stallman kirjoitti 20.04.2018 klo 06:53:
> [[[ 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. ]]]
>
> It sounds like Flatpak poses no free software ethical issues.
>
> > The flatpak
> > that I wrote for Emacs uses the org.freedesktop.Sdk runtime which to
> > my knowledge is entirely free software.
>
> "To my knowledge" means "as far as I know." Is that what you mean to
> say?
>
> If so, would you please verify that this runtime is indeed entirely
> made of free software? I would expect that is the case, but let's
> act based on knowledge rather than guessing.
>
Yes, this was based on somewhat vague knowledge and a bit of hopeful
assumption. But after some more looking into it, things still seem good
to me.
I got into contact with developers of Flatpak at the #flatpak channel on
the Freenode IRC network. According to them, only free software should
be included in the runtime. This is not very visibly documented
anywhere, but I was suggested to file them a request to add also such
documentation.
The runtime includes a description of names and versions of software
that is included. This comes in two separate parts [1,2] because of how
the runtime is built in two phases, with latter phase adding software on
top of the results from the first phase. I have browsed through these a
few times and did not notice anything that would be a problem. Mostly
the content looks like a typical small GNU/Linux distribution. However,
the runtime does not include the Linux kernel or firmware that is copied
into devices by some of the drivers that Linux includes. Thus the
relatively common issue with GNU/Linux distributions including
proprietary firmware should be absent.
[1]
https://gist.githubusercontent.com/muep/519ae7c718c80a8f6d83ff248f265dea/raw/f345a81067cd25a76959cef50ae14d2960e797e2/manifest.base
[2]
https://gist.githubusercontent.com/muep/17e52495f8eaee488c632fb962c124a1/raw/b9333c76a9d263d6d0623a8809a328e34315d6b1/manifest.json
next prev parent reply other threads:[~2018-04-20 18:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 17:55 Any interest in making Emacs available on Flathub? Joonas Sarajärvi
2018-04-18 19:31 ` Paul Eggert
2018-04-19 5:53 ` Joonas Sarajärvi
2018-04-19 22:42 ` Paul Eggert
2018-04-19 6:10 ` Richard Stallman
2018-04-19 7:06 ` Joonas Sarajärvi
2018-04-20 3:53 ` Richard Stallman
2018-04-20 18:39 ` Joonas Sarajärvi [this message]
2018-05-20 7:26 ` Joonas Sarajärvi
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=5b48cd55-429a-9a50-ad13-eaf0ac9a074b@iki.fi \
--to=muep@iki.fi \
--cc=emacs-devel@gnu.org \
--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 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.