From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Any interest in making Emacs available on Flathub? Date: Wed, 18 Apr 2018 12:31:48 -0700 Organization: UCLA Computer Science Department Message-ID: <85e0d7a6-a2e7-7d3e-8230-82cbb968c634@cs.ucla.edu> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1524079840 1148 195.159.176.226 (18 Apr 2018 19:30:40 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 18 Apr 2018 19:30:40 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 To: =?UTF-8?Q?Joonas_Saraj=c3=a4rvi?= , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 18 21:30:36 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f8smq-00005B-B1 for ged-emacs-devel@m.gmane.org; Wed, 18 Apr 2018 21:30:36 +0200 Original-Received: from localhost ([::1]:46688 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f8soo-0003TD-Cv for ged-emacs-devel@m.gmane.org; Wed, 18 Apr 2018 15:32:38 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51224) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f8soB-0003Sl-HB for emacs-devel@gnu.org; Wed, 18 Apr 2018 15:32:00 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f8so8-0000Vz-DJ for emacs-devel@gnu.org; Wed, 18 Apr 2018 15:31:59 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:41974) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1f8so8-0000V8-6V for emacs-devel@gnu.org; Wed, 18 Apr 2018 15:31:56 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id F188A16133D; Wed, 18 Apr 2018 12:31:52 -0700 (PDT) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 37G714p9JHu6; Wed, 18 Apr 2018 12:31:52 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id F398F1615E8; Wed, 18 Apr 2018 12:31:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 8sagG8i1XWPr; Wed, 18 Apr 2018 12:31:51 -0700 (PDT) Original-Received: from Penguin.CS.UCLA.EDU (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id DAF7716133D; Wed, 18 Apr 2018 12:31:51 -0700 (PDT) In-Reply-To: Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:224719 Archived-At: 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 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?