From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Alex Murray Newsgroups: gmane.emacs.devel Subject: Re: Emacs as a snap package Date: Thu, 23 May 2019 10:44:34 +0930 Message-ID: <87v9y20y6d.fsf@canonical.com> References: <87o93vnvza.fsf@canonical.com> <04296284-7d60-6cfb-1177-2928ee44023f@cs.ucla.edu> Reply-To: alex.murray@canonical.com Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="206136"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: mu4e 1.2.0; emacs 26.2 Cc: Richard Stallman To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 23 03:14:52 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hTcJo-000rWu-Ij for ged-emacs-devel@m.gmane.org; Thu, 23 May 2019 03:14:52 +0200 Original-Received: from localhost ([127.0.0.1]:55470 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hTcJn-00046y-EZ for ged-emacs-devel@m.gmane.org; Wed, 22 May 2019 21:14:51 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:58090) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hTcJg-00046o-HO for emacs-devel@gnu.org; Wed, 22 May 2019 21:14:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hTcJf-0006LE-N6 for emacs-devel@gnu.org; Wed, 22 May 2019 21:14:44 -0400 Original-Received: from youngberry.canonical.com ([91.189.89.112]:45336) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hTcJe-0006IJ-Aa; Wed, 22 May 2019 21:14:42 -0400 Original-Received: from 193-115-90-221.tpgi.com.au ([193.115.90.221] helo=slate) by youngberry.canonical.com with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1hTcJa-0002PO-Dd; Thu, 23 May 2019 01:14:39 +0000 In-reply-to: <04296284-7d60-6cfb-1177-2928ee44023f@cs.ucla.edu> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 91.189.89.112 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:236918 Archived-At: On Thu, 2019-05-23 at 03:14:27 +0930, Paul Eggert wrote: > I assume this has the function of the already-existing .gitlab-ci.yml file > that Emacs already has in the master branch. That file is for GitLab > continuous integration builds, whereas snapcraft.yaml would be for snap. > Similar but different - snap is both a build and a package mechanism - so it describes both the dependencies / how to build, plus packaging info such as version, description, sandboxing requirements etc. > This raises the issue: if we start supporting multiple CI platforms, > perhaps we should put build-instruction files into a new directory > (build-aux/ci, say), rather than cluttering the toplevel directory with > such files. > In general snapcraft.yaml would live in a snap/ subdirectory off the top-level. > >> 2. Register an official GNU Project account for the Snap store and use >> this to publish these official snap builds. >> >> 3. Optionally, use the build.snapcraft.io service to provide automated >> builds directly (similar to the current emacs-snapshot PPA[8] which is >> widely used). > > These are topics for RMS to address, I'd think. I'll CC: him.