Re: Emacs as a snap package

[Alex Murray <alex.murray@canonical.com>]

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.