unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: alex.murray@canonical.com
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: Emacs as a snap package
Date: Wed, 22 May 2019 10:44:27 -0700	[thread overview]
Message-ID: <04296284-7d60-6cfb-1177-2928ee44023f@cs.ucla.edu> (raw)
In-Reply-To: <87o93vnvza.fsf@canonical.com>

On 5/21/19 6:01 PM, Alex Murray wrote:
> As such I would be keen to get feedback on the following:
>
> 1. Maintain an official snapcraft.yaml recipe for Emacs within the Emacs
> git tree across both master and the various release branches which can
> be used to build 'official' Emacs snaps directly from the git source
> tree.

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.

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.


> 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.




  reply	other threads:[~2019-05-22 17:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22  1:01 Emacs as a snap package Alex Murray
2019-05-22 17:44 ` Paul Eggert [this message]
2019-05-23  1:14   ` Alex Murray

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=04296284-7d60-6cfb-1177-2928ee44023f@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=alex.murray@canonical.com \
    --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 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).