From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 0/2] Separation of isar images per machine
Date: Mon, 18 Mar 2019 00:01:27 +0100 [thread overview]
Message-ID: <20190317230129.17048-1-mosipov@ilbers.de> (raw)
Hello everybody,
This series is a result of discussion expressed in email
by Baurzhan Ismagulov at 14/03/2019:
>>>>>>>
Regarding the structure, I find the separation
tmp/work/${DISTRO}-${DISTRO_ARCH}/${MACHINE} more intuitive, since one can
clearly see from the directory structure what belongs together:
* ${DISTRO}-${DISTRO_ARCH} + machine1
* ${DISTRO}-${DISTRO_ARCH} + machine2
rather than
* ${DISTRO_ARCH}-${DISTRO} + all-${DISTRO} + machine1-${DISTRO}
* ${DISTRO_ARCH}-${DISTRO} + all-${DISTRO} + machine2-${DISTRO}
Besides, all-${DISTRO} requires careful consideration, since OE really builds
them once by default, whereas we would build the _all.debs for every arch. That
is a good point, because we could optimize some bits here (dpkg-buildpackage
--build=all).
>>>>>>>>
Regards,
Maxim.
Maxim Yu. Osipov (2):
classes/image: Unify and add missing extra stamps
meta-isar: Separate images per MACHINE
meta/classes/image.bbclass | 11 ++++++++---
meta/classes/isar-image.bbclass | 2 +-
2 files changed, 9 insertions(+), 4 deletions(-)
--
2.11.0
next reply other threads:[~2019-03-17 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 23:01 Maxim Yu. Osipov [this message]
2019-03-17 23:01 ` [PATCH 1/2] classes/image: Unify and add missing extra stamps Maxim Yu. Osipov
2019-03-17 23:01 ` [PATCH 2/2] meta-isar: Separate images per MACHINE Maxim Yu. Osipov
2019-03-19 10:39 ` [PATCH 0/2] Separation of isar images per machine 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=20190317230129.17048-1-mosipov@ilbers.de \
--to=mosipov@ilbers.de \
--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