From: Henning Schild <henning.schild@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH 3/3] buildchroot: Add prepare and cleanup tasks
Date: Tue, 21 Nov 2017 20:15:53 +0100 [thread overview]
Message-ID: <20171121201553.040b36b1@md1em3qc> (raw)
In-Reply-To: <20171121184940.5425-4-asmirnov@ilbers.de>
Please repost this with a use-case. At the moment i can only guess what
that could be used for. What is the Issue?
Henning
Am Tue, 21 Nov 2017 21:49:40 +0300
schrieb Alexander Smirnov <asmirnov@ilbers.de>:
> Some packages could require builchroot filesystem tunning, for
> example share Isar downloads folder with chroot filesystem.
>
> This patch adds two tasks for buildchroot:
>
> 1. 'do_prepare': This task is executed after buildchroot rootfs
> generation and before 'do_build' from packages to be built.
> Some notes:
> - An individual task is required for the case when you want to
> rebuild some package, this would require to run this preparation
> stuff for existing buildchroot rootfs.
> - This task should not have stamp. This means that anytime you want
> to build something, 'do_prepare' should be executed.
>
> 2. 'do_cleanup': This task is executed after all the packages are
> deployed. Some notes:
> - This task also should not have stamp.
> - This task depends from the recipes listed in IMAGE_INSTALL.
>
> Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
> ---
> meta/classes/dpkg-base.bbclass | 2 +-
> meta/classes/image.bbclass | 1 +
> meta/recipes-devtools/buildchroot/buildchroot.bb | 18
> ++++++++++++++++++ 3 files changed, 20 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/dpkg-base.bbclass
> b/meta/classes/dpkg-base.bbclass index 4941f9b..21ae88d 100644
> --- a/meta/classes/dpkg-base.bbclass
> +++ b/meta/classes/dpkg-base.bbclass
> @@ -2,7 +2,7 @@
> # Copyright (C) 2017 Siemens AG
>
> # Add dependency from buildchroot creation
> -do_build[depends] = "buildchroot:do_build"
> +do_build[depends] = "buildchroot:do_prepare"
>
> # Each package should have its own unique build folder, so use
> # recipe name as identifier
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 7813b16..b0f645c 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -83,6 +83,7 @@ do_populate() {
>
> addtask populate before do_build after do_unpack
> do_populate[deptask] = "do_deploy_deb"
> +do_populate[depends] = "buildchroot:do_cleanup"
>
> do_rootfs[stamp-extra-info] = "${MACHINE}-${DISTRO}"
>
> diff --git a/meta/recipes-devtools/buildchroot/buildchroot.bb
> b/meta/recipes-devtools/buildchroot/buildchroot.bb index
> 6a94733..4be094c 100644 ---
> a/meta/recipes-devtools/buildchroot/buildchroot.bb +++
> b/meta/recipes-devtools/buildchroot/buildchroot.bb @@ -71,3 +71,21 @@
> do_build() { sudo chroot ${BUILDCHROOT_DIR} /configscript.sh
> _do_build_cleanup
> }
> +
> +do_prepare[nostamp] = "1"
> +
> +do_prepare() {
> + bbnote "Prepare buildchroot for packages building"
> +}
> +
> +addtask prepare after do_build
> +
> +DEPENDS += "${IMAGE_INSTALL}"
> +do_cleanup[deptask] = "do_deploy_deb"
> +do_cleanup[nostamp] = "1"
> +
> +do_cleanup() {
> + bbnote "Cleanup buildchroot after packages building"
> +}
> +
> +addtask cleanup after do_prepare
next prev parent reply other threads:[~2017-11-21 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 18:49 [PATCH 0/3] Improvements Alexander Smirnov
2017-11-21 18:49 ` [PATCH 1/3] dpkg-base: Fix buildchroot dependency Alexander Smirnov
2017-11-21 19:10 ` Henning Schild
2017-11-21 19:33 ` Alexander Smirnov
2017-11-22 7:13 ` Christian Storm
2017-11-21 18:49 ` [PATCH 2/3] image: Add do_rootfs template to image class Alexander Smirnov
2017-11-21 18:49 ` [PATCH 3/3] buildchroot: Add prepare and cleanup tasks Alexander Smirnov
2017-11-21 19:15 ` Henning Schild [this message]
2017-11-21 19:36 ` 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=20171121201553.040b36b1@md1em3qc \
--to=henning.schild@siemens.com \
--cc=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