From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/2] dpkg: Allow parallel build of different package versions
Date: Tue, 11 Jan 2022 10:48:53 +0100 [thread overview]
Message-ID: <20220111104853.59bddc1c@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20220111093656.220514-2-amikan@ilbers.de>
Am Tue, 11 Jan 2022 12:36:55 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:
> To be able to use different versions of the same package for the
> different machines/multiconfigs we need to split workdir mount points
> and sstate manifests based on package version.
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
> meta/classes/dpkg-base.bbclass | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/dpkg-base.bbclass
> b/meta/classes/dpkg-base.bbclass index cb5ce4a..8850544 100644
> --- a/meta/classes/dpkg-base.bbclass
> +++ b/meta/classes/dpkg-base.bbclass
> @@ -158,8 +158,8 @@ def get_package_srcdir(d):
> return s
>
> # Each package should have its own unique build folder, so use
> -# recipe name as identifier
> -PP = "/home/builder/${PN}"
> +# recipe name and version as identifier
> +PP = "/home/builder/${P}"
Better go directly for PF to also cover PR
> PPS ?= "${@get_package_srcdir(d)}"
>
> # Empty do_prepare_build() implementation, to be overwritten if
> needed @@ -221,6 +221,9 @@ do_dpkg_build[cleandirs] +=
> "${DPKG_SSTATE}" do_dpkg_build[sstate-plaindirs] = "${DPKG_SSTATE}"
> do_dpkg_build[sstate-interceptfuncs] = "dpkg_build_sstate_prepare"
>
> +# Allow parallel build of different versions
> +SSTATE_MANFILEPREFIX .= "-${PV}"
I guess it should be
SSTATE_MANFILEPREFIX = "${SSTATE_MANIFESTS}/manifest-${SSTATE_MANMACH}-${PF}
or .= "${PV}-${PR}"
Henning
> dpkg_build_sstate_prepare() {
> test -n "$(find ${S}/.. -maxdepth 1 -name '*.deb' -print -quit)"
> && ln -f ${S}/../*.deb -t ${DPKG_SSTATE}
next prev parent reply other threads:[~2022-01-11 9:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 9:36 [PATCH 0/2] Fix u-boot-script packages conflict Anton Mikanovich
2022-01-11 9:36 ` [PATCH 1/2] dpkg: Allow parallel build of different package versions Anton Mikanovich
2022-01-11 9:48 ` Henning Schild [this message]
2022-01-11 9:36 ` [PATCH 2/2] u-boot-script: Split packages by kernel Anton Mikanovich
2022-01-11 9:50 ` Henning Schild
2022-01-11 12:03 ` Jan Kiszka
2022-01-11 15:05 ` Anton Mikanovich
2022-01-11 15:56 ` Jan Kiszka
2022-01-12 13:34 ` Anton Mikanovich
2022-01-12 13:51 ` Schmidt, Adriaan
2022-01-12 13:59 ` Jan Kiszka
2022-01-12 13:58 ` 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=20220111104853.59bddc1c@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=amikan@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