From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH 2/3] doc: Remove references to wheezy
Date: Mon, 20 Aug 2018 08:20:43 +0200 [thread overview]
Message-ID: <83002291d9b031002e00685c2f492dcd99b9dff4.1534746044.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1534746044.git.jan.kiszka@siemens.com>
In-Reply-To: <cover.1534746044.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
The next logical step to phase it out.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
doc/user_manual.md | 11 +++--------
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/doc/user_manual.md b/doc/user_manual.md
index c8f8ad9..d99f1f0 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -38,7 +38,6 @@ Isar provides:
For demonstration purposes, Isar provides support for the following
configurations:
- - QEMU ARM with Debian Wheezy
- QEMU ARM with Debian Jessie
- QEMU ARM with Debian Stretch (builds but fails to run, see #22)
- QEMU i386 with Debian Jessie
@@ -72,7 +71,6 @@ Notes:
* BitBake requires Python 3.4+.
* The python3 package is required for the correct `alternatives` setting.
* QEMU 2.8+ is required to run Stretch images locally in QEMU. This version is available in Stretch and Jessie backports apts.
-* e2fsprogs v1.42- required for building Wheezy images.
### Setup Sudo
@@ -137,7 +135,6 @@ a single call. List all configurations in `conf/local.conf`:
```
BBMULTICONFIG = " \
- qemuarm-wheezy \
qemuarm-jessie \
qemuarm-stretch \
qemui386-jessie \
@@ -151,7 +148,7 @@ BBMULTICONFIG = " \
The following command will produce `isar-image-base` images for all targets:
```
-$ bitbake multiconfig:qemuarm-wheezy:isar-image-base \
+$ bitbake \
multiconfig:qemuarm-jessie:isar-image-base \
multiconfig:qemuarm-stretch:isar-image-base \
multiconfig:qemui386-jessie:isar-image-base \
@@ -164,7 +161,6 @@ $ bitbake multiconfig:qemuarm-wheezy:isar-image-base \
Created images are:
```
-tmp/deploy/images/isar-image-base-debian-wheezy-qemuarm.ext4.img
tmp/deploy/images/isar-image-base-debian-jessie-qemuarm.ext4.img
tmp/deploy/images/isar-image-base-debian-stretch-qemuarm.ext4.img
tmp/deploy/images/isar-image-base-debian-jessie-qemui386.ext4.img
@@ -277,7 +273,7 @@ following variables define the default configuration to build for:
- `MACHINE` - The board to build for (e.g., `qemuarm`, `rpi`). BitBake looks
for conf/multiconfig/${MACHINE}.conf in every layer.
- - `DISTRO` - The distro to use (e.g., `debian-wheezy`, `raspbian-jessie`).
+ - `DISTRO` - The distro to use (e.g. `raspbian-jessie`, `debian-stretch`).
BitBake looks for conf/distro/${DISTRO}.conf in every layer.
- `DISTRO_ARCH` - The Debian architecture to build for (e.g., `armhf`).
@@ -307,7 +303,6 @@ Some other variables include:
In Isar, each machine can use its specific Linux distro to generate `buildchroot` and target filesystem. By default, Isar provides configuration files for the following distros:
- - debian-wheezy
- debian-jessie
- debian-stretch
- raspbian-jessie
@@ -367,8 +362,8 @@ To add new distro, user should perform the following steps:
- Create the `.conf` file in distro folder with the name of your distribution. We recommend to name distribution in the following format: `name`-`suite`, for example:
```
- debian-wheezy
debian-jessie
+ debian-stretch
```
- In this file, define the variables described above.
--
2.16.4
next prev parent reply other threads:[~2018-08-20 6:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 6:20 [PATCH 0/3] Cleanups, gitlab-ci update Jan Kiszka
2018-08-20 6:20 ` [PATCH 1/3] scripts: Remove build_parallel Jan Kiszka
2018-08-20 6:20 ` Jan Kiszka [this message]
2018-08-20 6:20 ` [PATCH 3/3] gitlab-ci: Update targets, add cross-compilation test Jan Kiszka
2018-08-27 22:09 ` [PATCH 0/3] Cleanups, gitlab-ci update Maxim Yu. Osipov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83002291d9b031002e00685c2f492dcd99b9dff4.1534746044.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox