From: Paul Eggert <eggert@cs.ucla.edu>
To: "Joonas Sarajärvi" <muep@iki.fi>, emacs-devel@gnu.org
Subject: Re: Any interest in making Emacs available on Flathub?
Date: Wed, 18 Apr 2018 12:31:48 -0700 [thread overview]
Message-ID: <85e0d7a6-a2e7-7d3e-8230-82cbb968c634@cs.ucla.edu> (raw)
In-Reply-To: <adc131a9-e685-02b5-e45f-b3e1ecce154e@iki.fi>
It'd be helpful to have Emacs easily distributable via Flatpak. Since
I'm not a Flatpak expert, could you help fill us in on what's needed? In
your draft <https://bitbucket.org/muep/org.gnu.emacs/> I see three files:
* A patch to src/xterm.c that is installed on Savannah, so this is done
already (in the next Emacs version, anyway).
* Adding info about release 25.3 to etc/emacs.appdata.xml. Should this
info be all the Emacs releases (see etc/HISTORY) or just the releases
tuned for Flatpak? If so, presumably it should start with the first
release that works well with Flatpak.
* A file org.gnu.Emacs.json, which I suppose we could copy to
etc/org.gnu.Emacs.json in the master Emacs distribution. Or perhaps
there's another better place for it? How should this file evolve as
Emacs makes further releases? Presumably each release should clear out
the patches from the "modules" section?
A few more questions:
* I notice that your org.gnu.Emacs.json file differs from that of
others. Is it important that this file be reasonably standard for
everybody's convenience, or is it merely a template for people to
configure? Is it something that "make" should construct, when you're
building Emacs? That sort of thing.
* Would it make sense for the top-level Emacs makefile to have a
"flatpak" action, so that "make flatpak" does something for Flatpak that
"make install" does for a native installation? If so, what should "make
flatpak" do?
* If we want to also support AppImage, Snap, etc., how should we arrange
for this in an economical and intuitive way in the source?
next prev parent reply other threads:[~2018-04-18 19:31 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 [this message]
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
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
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=85e0d7a6-a2e7-7d3e-8230-82cbb968c634@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=muep@iki.fi \
/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).