Merge lp:~michael.nelson/snapcraft/fix-golang-tutorial-to-match-changes-from-r132 into lp:~snappy-dev/snapcraft/core

[Michael Nelson]

Fix snapcraft.yaml's reference to go-package plugin to match changes in r132.

Without this, following the tutorial results in:

$ snapcraft stage
Unknown plugin: go1.4-project
Could not load part go1.4-project

Currently, if you try to add a:

    snappy-metadata: meta

to your snapcraft.yaml, you'll see an error [1]. Turns out the metadata is now expected in the snapcraft.yaml itself, so README updated to match that after testing locally.

[1] http://paste.ubuntu.com/12270254/

[lp:~michael.nelson/snapcraft/fix-golang-tutorial-to-match-changes-from-r132]

152. By Michael Nelson on 2015-09-04

Update your-first-snap now that metadata is in the snapcraft.yaml file itself.

[Sergio Schvezov (sergiusens)]

it all looks good, thanks, just maybe pick a different a icon?

[lp:~michael.nelson/snapcraft/fix-golang-tutorial-to-match-changes-from-r132]

153. By Michael Nelson on 2015-09-07

Switch example icon to text-x-apport.png

[Michael Nelson (michael.nelson)]

On Mon, Sep 7, 2015 at 11:21 PM Sergio Schvezov <
<email address hidden>> wrote:

> it all looks good, thanks, just maybe pick a different a icon?
>
> Diff comments:
>
> > === modified file 'docs/your-first-snap.md'
> > --- docs/your-first-snap.md 2015-08-05 13:38:39 +0000
> > +++ docs/your-first-snap.md 2015-09-04 03:24:38 +0000
> > @@ -213,9 +205,12 @@
> > plugin: copy
> > files:
> > webcam-webui: bin/webcam-webui
> > - snappy-metadata: meta
> > -
> > -And tell Snapcraft to actually make the snap package:
> > +
> > +Copy a png icon of your choice into your current directory:
> > +
> > + $ cp /usr/share/icons/hicolor/256x256/apps/unity-datetime-panel.png
> ./icon.png
>
> how about a different icon?
>
>
Done. It's just an example to run the demo (as the icon is now required),
but I've switch it
to /usr/share/icons/hicolor/64/mimetypes/text-x-apport.png

[Sergio Schvezov (sergiusens)]

review: Approve

[Sergio Schvezov (sergiusens)]

Ok, thanks! I'll improve snapcraft init to get a 'template' of the required fields soon, it's one of the reasons I disabled daily builds as of yet.

=== modified file 'docs/your-first-snap.md'
--- docs/your-first-snap.md	2015-08-05 13:38:39 +0000
+++ docs/your-first-snap.md	2015-09-07 13:30:28 +0000
@@ -70,14 +70,13 @@
 
     parts:
       golang-static-http:
-        plugin: go1.4-project
+        plugin: go-project
         source: git://github.com/mikix/golang-static-http
 
 You've got a `parts` list with one item, named `golang-static-http`, but we
 could call it anything. That part has a few options. A `plugin` option that
-tells Snapcraft how to interpret the part. In this case, it's a Go project
-using Go 1.4. And finally, a `source` option telling Snapcraft where to
-download the code.
+tells Snapcraft how to interpret the part. In this case, it's a Go project.
+And finally, a `source` option telling Snapcraft where to download the code.
 
 Go ahead and create `snapcraft.yaml` with the above contents in an empty
 directory.
@@ -104,7 +103,7 @@
 
     parts:
       golang-static-http:
-        plugin: go1.4-project
+        plugin: go-project
         source: git://github.com/mikix/golang-static-http
       fswebcam:
         plugin: ubuntu
@@ -153,7 +152,7 @@
 
     parts:
       golang-static-http:
-        plugin: go1.4-project
+        plugin: go-project
         source: git://github.com/mikix/golang-static-http
       fswebcam:
         plugin: ubuntu
@@ -179,14 +178,13 @@
 ### Package Metadata
 
 "But how do we actually make a snap?", you may be wondering. To do that, we
-need some metadata files required by Snappy that describe how our code should
-be installed and run.
+need to add some Snappy metadata that describes how our code should be
+installed and run.
 
 You can read all about the [format of this metadata](https://developer.ubuntu.com/en/snappy/guides/packaging-format-apps/),
 but we'll assume here that you're already familiar.
 
-Let's make a new subdirectory called `meta` and put our Snappy package files
-there. Here's the contents of `meta/package.yaml`:
+Let's add some metadata to our snapcraft file
 
     name: webcam-webui
     version: 1
@@ -194,18 +192,12 @@
     services:
     - name: webcam-webui
       start: bin/webcam-webui
-
-And a very simple `meta/readme.md`:
-
-    # Webcam web UI
-
-    Exposes your webcam over a web UI
-
-Now that we have that sorted, we can tell Snapcraft where to find our metadata:
-
+    summary: Webcam web UI
+    description: Exposes your webcam over a web UI
+    icon: icon.png
     parts:
       golang-static-http:
-        plugin: go1.4-project
+        plugin: go-project
         source: git://github.com/mikix/golang-static-http
       fswebcam:
         plugin: ubuntu
@@ -213,9 +205,12 @@
         plugin: copy
         files:
           webcam-webui: bin/webcam-webui
-    snappy-metadata: meta
-
-And tell Snapcraft to actually make the snap package:
+
+Copy a png icon of your choice into your current directory:
+
+    $ cp /usr/share/icons/hicolor/64/mimetypes/text-x-apport.png ./icon.png
+
+and tell Snapcraft to actually make the snap package:
 
     $ snapcraft assemble