public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>,
	<sven.schultschik@siemens.com>, <cedric_hombourger@mentor.com>
Subject: Re: [PATCH 1/2] meta-isar: example-raw: Fix misuse of ${S}
Date: Tue, 14 Apr 2020 09:02:12 +0200	[thread overview]
Message-ID: <20200414090212.57b9d9cf@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <492d3274ed96f0fe39ff50a3c8ddd9ad45f66830.1585926177.git.jan.kiszka@siemens.com>

Am Fri, 3 Apr 2020 17:02:56 +0200
schrieb Jan Kiszka <jan.kiszka@siemens.com>:

> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> We shall install into ${D}, not ${S}. This will break once dpkg-raw
> makes both deviate.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>  meta-isar/recipes-app/example-raw/example-raw_0.3.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta-isar/recipes-app/example-raw/example-raw_0.3.bb
> b/meta-isar/recipes-app/example-raw/example-raw_0.3.bb index
> e4921709..21664642 100644 ---
> a/meta-isar/recipes-app/example-raw/example-raw_0.3.bb +++
> b/meta-isar/recipes-app/example-raw/example-raw_0.3.bb @@ -35,10
> +35,10 @@ do_install() { bbnote "A HOME entry for everyone ...
> created after this is installed" echo "hello skel" >
> ${WORKDIR}/${PN}-isar-skel.txt install -v -d ${D}/etc/skel/
> -	install -v -m 644 ${WORKDIR}/${PN}-isar-skel.txt
> ${S}/etc/skel/
> +	install -v -m 644 ${WORKDIR}/${PN}-isar-skel.txt
> ${D}/etc/skel/ 
>  	bbnote "A user-specific HOME entry"
>  	echo "hello isar" > ${WORKDIR}/${PN}-isar.txt
>  	install -v -d ${D}/var/lib/isar/
> -	install -v -m 644 ${WORKDIR}/${PN}-isar.txt
> ${S}/var/lib/isar/
> +	install -v -m 644 ${WORKDIR}/${PN}-isar.txt
> ${D}/var/lib/isar/ }

While this is correct it strongly suggests we will see similar problems
in downstream layers once the other patch gets applied.

We do not actually change the API, but i think an entry in the
changelog might still be a good idea.

Henning

  reply	other threads:[~2020-04-14  7:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 15:02 [PATCH 0/2] Fix dpkg-raw usage of and Jan Kiszka
2020-04-03 15:02 ` [PATCH 1/2] meta-isar: example-raw: Fix misuse of ${S} Jan Kiszka
2020-04-14  7:02   ` Henning Schild [this message]
2020-04-03 15:02 ` [PATCH 2/2] dpkg-raw: Correct path so that git fetching works Jan Kiszka
2020-04-14  7:05   ` Henning Schild
2020-04-14  7:11     ` Henning Schild
2020-04-14  7:53       ` Jan Kiszka
2020-04-14  7:15     ` Jan Kiszka
2020-04-14  7:34   ` [PATCH v2 " Jan Kiszka
2020-04-17 15:32     ` Baurzhan Ismagulov
2020-05-06 19:29     ` Baurzhan Ismagulov
2020-04-06  6:01 ` [PATCH 0/2] Fix dpkg-raw usage of and Jan Kiszka

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=20200414090212.57b9d9cf@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=cedric_hombourger@mentor.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=sven.schultschik@siemens.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