Merge pull request mendersoftware#400 from TheYoctoJester/scarthgap_c…

…leanups

Minor clarifications and clean-ups, no functional changes

.github/workflows/build.yml

@@ -1,7 +1,7 @@
 name: build boards
 
 on:
- push:
+ workflow_dispatch:
  schedule:
  # * is a special character in YAML so you have to quote this string
  - cron: '5 2 * * 6'

README.md

@@ -105,65 +105,6 @@ Requirements:
 - the primary targetted branch must be a Yocto Project LTS correlated one
 - add your board to the automated build configuration at `.github/workflows/build.yml`, marked as `experimental`. It will be moved out of experimental after a number of successful builds by the Mender team.
 
-### Google repo
-
-**Note: `repo` support is currently kept for compatibility reasons but will be removed in the future.**
-
-#### Manifest files
-
-The google repo tool and associated manifest files are used for managing the
-list of repositories needed for these builds. The common manifests
-(meta-mender-community/scripts/mender.xml) is included by board-specific
-manifests and include the required Mender layers:
-
- meta-mender-community/scripts/mender.xml
-
-This includes the required Mender layers,
-[meta-mender](https:/mendersoftware/meta-mender) and
-[meta-mender-community](https:/mendersoftware/meta-mender-community).
-
-Each integration layer should provide a manifest file, e.g
-
- meta-mender-community/meta-mender-sunxi/scripts/manifest-sunxi.xml
-
-#### Templates and configuration fragments
-
-To use this layer:
-
-1. Download the source:
-
-```
- $ mkdir mender-<vendor/soc name>
- $ cd mender-<vendor/soc name>
- $ repo init \
- -u https:/mendersoftware/meta-mender-community \
- -m meta-mender-<vendor/soc name>/scripts/manifest-<vendor/soc name>.xml \
- -b kirkstone
- $ repo sync
-```
-
-2. Setup environment:
-
-```
- $ . ./setup-environment <vendor/soc name>
-```
-
-3. Build:
-
-```
- $ bitbake core-image-base
-```
-
-The `setup-environment` script provided is a wrapper for the Yocto
-`oe-init-build-env` script.
-
-Each integration layer must provide:
-
-- local.conf.append: this contains board-specific changes to be appended to
-the Yocto-generated local.conf file
-- bblayers.conf.sample: a template that will be copied to bblayers.conf
-- an entry in [setup-environment](https:/mendersoftware/meta-mender-community/blob/rocko/scripts/setup-environment#L20-L25)
-
 ## Contributing
 
 We welcome and ask for your contribution. If you would like to contribute to

meta-mender-beaglebone/README.md

@@ -30,18 +30,7 @@ revision: HEAD
 
 ## Quick start
 
-The following commands will setup the environment and allow you to build images
-that have Mender integrated.
-
-
-```
-mkdir mender-beaglebone && cd mender-beaglebone
-repo init -u https:/mendersoftware/meta-mender-community \
- -m meta-mender-beaglebone/scripts/manifest-beaglebone.xml \
- -b kirkstone
-repo sync
-source setup-environment beaglebone
-bitbake core-image-base
-```
-
+See the top level [README](../README.md) for instructions to build using the `kas` tool. Supported configurations are
 
+- [`beaglebone.yml`](../kas/beaglebone.yml)
+- [`beaglebone-uboot.yml`](../kas/beaglebone-uboot.yml)