From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH 3/3] doc: Fix licenses path in user manual
Date: Fri, 18 Jan 2019 17:24:40 +0100 [thread overview]
Message-ID: <74b24ea1e9796533eec84c61b8da940f908ed49a.1547828680.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1547828680.git.jan.kiszka@siemens.com>
In-Reply-To: <cover.1547828680.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
Moved into core layer by now.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
doc/user_manual.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/user_manual.md b/doc/user_manual.md
index 2aa291d..42e940c 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -507,7 +507,7 @@ installation by appending them to the `IMAGE_PREINSTALL` variable while packages
DESCRIPTION = "Sample image recipe for ISAR"
LICENSE = "gpl-2.0"
-LIC_FILES_CHKSUM = "file://${LAYERDIR_isar}/licenses/COPYING.GPLv2;md5=751419260aa954499f7abaabaa882bbe"
+LIC_FILES_CHKSUM = "file://${LAYERDIR_core}/licenses/COPYING.GPLv2;md5=751419260aa954499f7abaabaa882bbe"
PV = "1.0"
@@ -546,7 +546,7 @@ The `deb` packages are built using `dpkg-buildpackage`, so the sources should co
DESCRIPTION = "Sample application for ISAR"
LICENSE = "gpl-2.0"
-LIC_FILES_CHKSUM = "file://${LAYERDIR_isar}/licenses/COPYING.GPLv2;md5=751419260aa954499f7abaabaa882bbe"
+LIC_FILES_CHKSUM = "file://${LAYERDIR_core}/licenses/COPYING.GPLv2;md5=751419260aa954499f7abaabaa882bbe"
PV = "1.0"
@@ -565,7 +565,7 @@ The following variables are used in this recipe:
- `LIC_FILES_CHKSUM` - Reference to the license file with its checksum. Isar recommends to store license files for your applications into layer your layer folder `meta-user/licenses/`. Then you may reference it in recipe using the following path:
```
- LIC_FILES_CHKSUM = file://${LAYERDIR_isar}/licenses/...
+ LIC_FILES_CHKSUM = file://${LAYERDIR_core}/licenses/...
```
This approach prevents duplication of the license files in different packages.
--
2.16.4
next prev parent reply other threads:[~2019-01-18 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 16:24 [PATCH 0/3] Follow-up fixes to meta/meta-isar reorganisation Jan Kiszka
2019-01-18 16:24 ` [PATCH 1/3] isar-image: Allow paths in DISTRO_CONFIG_SCRIPT Jan Kiszka
2019-01-18 16:24 ` [PATCH 2/3] Remove last reference from meta to meta-isar Jan Kiszka
2019-01-18 16:24 ` Jan Kiszka [this message]
2019-01-23 13:41 ` [PATCH 0/3] Follow-up fixes to meta/meta-isar reorganisation 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=74b24ea1e9796533eec84c61b8da940f908ed49a.1547828680.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