From: Henning Schild <henning.schild@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 2/4] meta-isar-bin: Generate cache repos
Date: Wed, 20 Sep 2017 10:11:59 +0200 [thread overview]
Message-ID: <20170920101159.5b086d0c@md1em3qc> (raw)
In-Reply-To: <20170919122052.28688-3-asmirnov@ilbers.de>
Am Tue, 19 Sep 2017 15:20:50 +0300
schrieb Alexander Smirnov <asmirnov@ilbers.de>:
> Generate repos for each configuration in multiconfig.
>
> Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
> ---
> meta-isar-bin/conf/layer.conf | 3 +++
> meta/classes/image.bbclass | 14 ++++++++++++++
> 2 files changed, 17 insertions(+)
>
> diff --git a/meta-isar-bin/conf/layer.conf
> b/meta-isar-bin/conf/layer.conf index 3518184..5ef6e60 100644
> --- a/meta-isar-bin/conf/layer.conf
> +++ b/meta-isar-bin/conf/layer.conf
> @@ -9,3 +9,6 @@ DEBCACHEDIR ?= "${LAYERDIR}/apt"
>
> # Path to the configuration files templates used by `reprepro`
> DEBFILESDIR ?= "${LAYERDIR}/files"
> +
> +# Path to the databases used by `reprepro`
> +DEBDBDIR ?= "${LAYERDIR}/db"
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 30f241a..9db7371 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -35,6 +35,20 @@ python __anonymous () {
> f.close()
> }
>
> +do_create_cache_db[stamp-extra-info] = "${DISTRO}"
> +
> +do_create_cache_db() {
> + path_cache="${DEBCACHEDIR}/${DISTRO}"
> + path_databases="${DEBDBDIR}/${DISTRO}"
> +
> + if [ ! -d "${path_databases}" ]; then
> + reprepro --waitforlock 3 -b ${path_cache} --dbdir
> ${path_databases} \
> + export ${DEBDISTRONAME}
> + fi
> +}
> +
> +addtask create_cache_db before do_fetch
This adds a new tool dependency, maybe update docs with the patch or
keep in mind for later.
Why "waitforlock 3" is there any chance at all that multiple images run
into that at the same time? And if so how do we know 3 is enough? I just
tested that a second "reprepro export" will still return 0, so it seems
safe to do that multiple times, not sure what would happen if some
packages where already added and you "export" again.
Henning
> do_populate[stamp-extra-info] = "${DISTRO}-${MACHINE}"
>
> # Install Debian packages, that were built from sources
next prev parent reply other threads:[~2017-09-20 8:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 12:20 [PATCH v2 0/4] Basic binary cache implementation Alexander Smirnov
2017-09-19 12:20 ` [PATCH v2 1/4] meta-isar-bin: Add reprepro configs Alexander Smirnov
2017-09-20 7:58 ` Henning Schild
2017-09-20 8:12 ` Alexander Smirnov
2017-09-20 8:38 ` Henning Schild
2017-09-20 8:51 ` Alexander Smirnov
2017-09-19 12:20 ` [PATCH v2 2/4] meta-isar-bin: Generate cache repos Alexander Smirnov
2017-09-20 8:11 ` Henning Schild [this message]
2017-09-20 8:26 ` Alexander Smirnov
2017-09-21 8:55 ` Andreas Reichel
2017-09-21 9:21 ` Claudius Heine
2017-09-22 10:56 ` Baurzhan Ismagulov
2017-09-25 10:49 ` Claudius Heine
2017-09-25 11:57 ` Alexander Smirnov
2017-09-25 13:48 ` Claudius Heine
2017-09-19 12:20 ` [PATCH v2 3/4] meta-isar-bin: Populate cache Alexander Smirnov
2017-09-20 8:22 ` Henning Schild
2017-09-20 8:49 ` Alexander Smirnov
2017-09-19 12:20 ` [PATCH v2 4/4] meta-isar-bin: Install packages via multistrap Alexander Smirnov
2017-09-20 8:28 ` Henning Schild
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=20170920101159.5b086d0c@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