From: Alexander Smirnov <asmirnov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: dpkg-base.bbclass: Mistake in stamp name?
Date: Wed, 14 Feb 2018 20:10:05 +0300 [thread overview]
Message-ID: <5aba504e-89da-768f-7e9e-2f9310c00aa2@ilbers.de> (raw)
In-Reply-To: <2cbcf30f-e51b-4e05-82a1-cd7ec5c03746@siemens.com>
On 02/14/2018 06:56 PM, Jan Kiszka wrote:
> addtask deploy_deb after do_build
> do_deploy_deb[stamp-extra-info] = "${DISTRO}-${MACHINE}"
>
> Shouldn't this be "${DISTRO}-${DISTRO_ARCH}"?
Huh, good finding. IIRC initially there was issue with RPi and qemuarm.
Both of these boards have the same ${DISTRO_ARCH}.
1. Initially Isar supported only one Debian distribution, so to
distinguish stamps between machines, the ${MACHINE} suffix was used.
2. Then another distribution was added, but there was no split in
${TMPDIR} like you see now, ${WORKDIRS} were split by distro or arch
name only, so RPi and qemuarm had shared working directory.
3. Some tasks were shared for example do_unpack for qemuarm and rpi, but
some tasks like do_build and do_deploy should run per-machine.
4. Some stamps were fixed after splitting of ${TMPDIR}, seems this one
was missed.
For now I guess this makes no sense, we have complete split of
workspaces in ${TMPDIR}. So "${DISTRO}-${DISTRO_ARCH}" could be used.
But your question pointed me to another topic:
1. We have two armhf boards, let's say Rpi1 and RPi2.
2. I want two Jessie images for this boards.
3. How we should process them in Isar? With current layout the only one
configuration will be compiled. How kernel packages should be distinguished?
Alex
next prev parent reply other threads:[~2018-02-14 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 15:56 Jan Kiszka
2018-02-14 17:10 ` Alexander Smirnov [this message]
2018-02-14 17:28 ` 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=5aba504e-89da-768f-7e9e-2f9310c00aa2@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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