From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users@googlegroups.com
Cc: Alexander Smirnov <asmirnov@ilbers.de>
Subject: [PATCH v3 0/5] Unify work space for packages
Date: Mon, 11 Sep 2017 22:27:33 +0300 [thread overview]
Message-ID: <20170911192738.1323-1-asmirnov@ilbers.de> (raw)
Hi all,
this series does the following:
- Simplifies folders structure for multiconfig.
- Unifies work space for packages.
- Use unified canonical names for build artifacts.
The overal build tree with multiconfig looks like the following:
$ ls -1 tmp/work/
debian-jessie-amd64
debian-jessie-armhf
debian-jessie-i386
debian-stretch-amd64
debian-stretch-armhf
debian-stretch-i386
debian-wheezy-armhf
raspbian-jessie-armhf
Package workdir looks now like the following:
$ ls -1 tmp/work/debian-jessie-amd64/hello-0.1+g7f35942-1-r0/
git
hello_0.1+g7f35942-1_amd64.changes
hello_0.1+g7f35942-1_amd64.deb
hello_0.1+g7f35942-1.dsc
hello_0.1+g7f35942-1.tar.gz
temp
Changes since v2:
- PATCH 1: Typo in commit message.
- PATCH 2: Drop WORKDIR_RELATIVE and WORKDIR_NAME from bibtbake.conf,
get relative path using inline python call,
replace multiple sed call by single one.
- PATCH 5: Update comment to be correct.
Changes since v1:
- Split first patch into pieces.
- Use variable in multistrap config.
- Rename ext4 image to unified cacnonical name (patch 4).
With best regards,
Alex
Alexander Smirnov (5):
image: Unify path to image rootfs
isar: Change build folders tree
stamps: Name stamps canonicaly and unified
image: Name image canonicaly and unified
class/dpkg: Unify workplace for packages
meta-isar/classes/rpi-sdimg.bbclass | 2 +-
meta-isar/recipes-core/images/isar-image-base.bb | 18 ++++++++----------
meta/classes/dpkg.bbclass | 15 +++++++++------
meta/classes/ext4-img.bbclass | 12 ++++++------
meta/classes/image.bbclass | 11 ++++++-----
meta/conf/isar-bitbake.conf | 5 ++++-
meta/recipes-devtools/buildchroot/buildchroot.bb | 8 ++++----
scripts/start_vm | 2 +-
8 files changed, 39 insertions(+), 34 deletions(-)
--
2.1.4
next reply other threads:[~2017-09-11 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 19:27 Alexander Smirnov [this message]
2017-09-11 19:27 ` [PATCH v3 1/5] image: Unify path to image rootfs Alexander Smirnov
2017-09-11 19:27 ` [PATCH v3 2/5] isar: Change build folders tree Alexander Smirnov
2017-09-12 7:23 ` Claudius Heine
2017-09-12 7:57 ` Alexander Smirnov
2017-09-12 12:52 ` Henning Schild
2017-09-12 13:02 ` Alexander Smirnov
2017-09-11 19:27 ` [PATCH v3 3/5] stamps: Name stamps canonicaly and unified Alexander Smirnov
2017-09-11 19:27 ` [PATCH v3 4/5] image: Name image " Alexander Smirnov
2017-09-11 19:27 ` [PATCH v3 5/5] class/dpkg: Unify workplace for packages Alexander Smirnov
2017-09-12 14:26 ` [PATCH] doc: Update technical overview Alexander Smirnov
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=20170911192738.1323-1-asmirnov@ilbers.de \
--to=asmirnov@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