git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Snapping git

From
APAlan Pope <alan.pope@canonical.com>
Date
May 10, 2017, 10:35 UTC
Message-ID
<CAMxnTANw-eMhju1qMr8Vgq5j-8t0AU6yj2fCJmMhowgAp=tzmw@mail.gmail.com>
Hello!

I work at Canonical as part of the engineering team around Ubuntu and Snapcraft [1].

We’re working on snaps, a platform to enable ISVs to directly control delivery of software updates to their users, and make their software available on many Linux distributions to a wide audience via our snappy store.

Snaps enable you to have the latest build of git available directly from github master to adventurous users in minutes, and your stable tagged releases to more conservative users automatically.

Ideally I'm looking for someone in the community who can spend a little bit of time over the next week or so creating a snap package out of the latest source from git master. We have documentation [2] and a forum [3] where the snap developers and users hang out. We're keen to find out where the rough edges are in our docs / process, and improve them, so feedback (+ve/-ve) from this process is essential to us.

Ultimately the outcome would be a single package in the snap store 'edge' channel which has the latest git master build that adventurous developers on various Linux [4] distributions can install with a simple 'snap install git --edge'.

Anyone fancy taking on this challenge? :)

[1] http://snapcraft.io/ [2] http://snapcraft.io/docs [3] http://forum.snapcraft.io/ [4] https://snapcraft.io/docs/core/install

Best regards
-- 
Alan Pope
Snap Advocate

Canonical - Ubuntu Engineering and Services
+44 (0) 7973 620 164
alan.pope@canonical.com
http://ubuntu.com/
Message 1 of 1 in “Snapping git”
  1. Alan PopeMay 10, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.