Pull request #38: Refactor/images

Merge in ICO/coreos from refactor/images to master

* commit '0b3e395862d9dea90a9c170c3a48a12fd985e3c6':
  chore(coreos-image-minimal-dev): delete the recipes
  refactor: rename coreos-image-full-cmdline to coreos-image-demo

documentation/quick-build.rst

@@ -99,11 +99,11 @@ the machine is set to `cn9130-cf-pro` but you can use any other MACHINE listed i
     occurrences of `cn9130-cf-pro` to your machine when executing a command.
 
 For an image that contains a lot of developer tools, the best image to build
-is `coreos-image-full-cmdline`.
+is `coreos-image-demo`.
 
 .. code-block:: sh
 
-   ~/img-build/build$ bitbake coreos-image-full-cmdline
+   ~/img-build/build$ bitbake coreos-image-demo
 
 After a long time, the build system will return. You can list all the artifacts
 produced by `bitbake` using `ls`:
@@ -118,7 +118,7 @@ be found with this command:
 .. code-block:: sh
 
    ~/coreos/build$ find tmp/deploy/images/${MACHINE} -type l -name "*.wic.xz"
-   tmp/deploy/images/cn9130-cf-pro/coreos-image-full-cmdline-cn9130-cf-pro.wic.xz
+   tmp/deploy/images/cn9130-cf-pro/coreos-image-demo-cn9130-cf-pro.wic.xz
 
 .. hint::
 
@@ -166,6 +166,6 @@ Now, flash the image file to the your card:
 
 .. code-block:: sh
 
-   ~/coreos/build$ bmaptool copy tmp/deploy/images/cn9130-cf-pro/coreos-image-full-cmdline-cn9130-cf-pro.wic.xz /dev/<DISKNAME>
+   ~/coreos/build$ bmaptool copy tmp/deploy/images/cn9130-cf-pro/coreos-image-demo-cn9130-cf-pro.wic.xz /dev/<DISKNAME>
 
 You have to replace `<DISKNAME>` by the name of your SD Card device.

documentation/ref-manual/images.rst

@@ -4,12 +4,12 @@ Images
 
 The CoreOS build system provides several examples image:
 
-.. index:: coreos-image-full-cmdline
+.. index:: coreos-image-demo
 
-``coreos-image-full-cmdline``
+``coreos-image-demo``
 =============================
 
- A console-only image with more full-featured Linux system functionality installed.
+ A image with most of the optional feature of CoreOS.
 
 .. index:: coreos-image-minimal
 

layers/meta-belden-coreos/recipes-core/images/coreos-image-demo.bb

@@ -1,5 +1,4 @@
-DESCRIPTION = "A console-only image with more full-featured Linux system \
+DESCRIPTION = "An image that come with most of the feature available in CoreOS"
-functionality installed."
 
 inherit coreos-image
 

layers/meta-belden-coreos/recipes-core/images/coreos-image-minimal-dev.bb

@@ -1,6 +0,0 @@
-require coreos-image-minimal.bb
-
-DESCRIPTION = "A small image just capable of allowing a device to boot and \
-is suitable for development work."
-
-IMAGE_FEATURES += "dev-pkgs dev-tools"

templates/conf-notes.txt

@@ -11,15 +11,14 @@ You can now run 'bitbake <target>'
 
 Common targets are:
     coreos-image-minimal
-    coreos-image-full-cmdline
+    coreos-image-demo
-    meta-toolchain
-    meta-ide-support
 
 You can also run generated qemu images with a command like 'runqemu qemuarm64'.
 
 Other commonly useful commands are:
  - 'devtool' and 'recipetool' handle common recipe tasks
  - 'bitbake-layers' handles common layer tasks
+ - 'bitbake-getvar' query the value of a variable
  - 'oe-pkgdata-util' handles common target package tasks
 
 You can open the CoreOS documentation by running the 'coreos-doc' command.