From: Henning Schild <henning.schild@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH] Use GBP_EXPORT_ORIG_OPTIONS for dpg-gbp export command
Date: Wed, 4 Jan 2023 09:28:47 +0100 [thread overview]
Message-ID: <20230104092847.27e284f6@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20230104065141.8984-1-ubely@ilbers.de>
Am Wed, 4 Jan 2023 07:51:41 +0100
schrieb Uladzimir Bely <ubely@ilbers.de>:
> Since we now use `gbp export-orig <options>` and they need different
> options than `gbp buildpackage`, we should store these options in
> different variable.
>
> This patch intruduces `GBP_EXPORT_ORIG_OPTINS`
GBP_EXPORT_ORIG_OPTIONS
> variable and
> describes it in RECIPE-API-CHANGELOG.
>
> Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> ---
> RECIPE-API-CHANGELOG.md | 16 ++++++++++++++++
> meta/classes/dpkg-gbp.bbclass | 4 ++--
> 2 files changed, 18 insertions(+), 2 deletions(-)
>
> diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
> index 0bb83389..8013e585 100644
> --- a/RECIPE-API-CHANGELOG.md
> +++ b/RECIPE-API-CHANGELOG.md
> @@ -441,3 +441,19 @@ exist, empty variables are forwarded.
>
> **Note about reproducibility**: the forwarded variables must not
> have any influence on the generated package. This mechanism must also
> not be used to inject build configurations. For these cases,
> templates should be used. + +### Switch to `gbp export-orig` and
> `GBP_EXPORT_ORIG_OPTIONS` +
> +Since Debian Stretch support is removed, we can now use short `gbp
> export-orig` +instead of long `gbp buildpackage --git-ignore-new
> --git-builder=/bin/true` +to prepare gbp-based sources for building.
> +
> +Options for `export-orig` should be specified with
> `GBP_EXPORT_ORIG_OPTIONS` +variable in favor of previously used
> `GBP_EXTRA_OPTIONS` one. For example: +
> +```
> +GBP_EXTRA_OPTIONS = "--git-no-pristine-tar
> --git-upstream-branch=master" +GBP_EXPORT_ORIG_OPTIONS =
> "--no-pristine-tar --upstream-branch=master" +```
> +
> +To support both old and new Isar, custom recipe should have both
> variables. diff --git a/meta/classes/dpkg-gbp.bbclass
> b/meta/classes/dpkg-gbp.bbclass index f765eb9a..4e29f62d 100644
> --- a/meta/classes/dpkg-gbp.bbclass
> +++ b/meta/classes/dpkg-gbp.bbclass
> @@ -9,13 +9,13 @@ S = "${WORKDIR}/git"
>
> PATCHTOOL ?= "git"
>
> -GBP_EXTRA_OPTIONS ?= "--pristine-tar"
> +GBP_EXPORT_ORIG_OPTIONS ?= "--pristine-tar"
>
> SCHROOT_MOUNTS = "${WORKDIR}:${PP} ${GITDIR}:/home/.git-downloads"
>
> dpkg_runbuild_prepend() {
> sh -c "
> cd ${WORKDIR}/${PPS}
> - gbp export-orig ${GBP_EXTRA_OPTIONS}
> + gbp export-orig ${GBP_EXPORT_ORIG_OPTIONS}
> "
> }
prev parent reply other threads:[~2023-01-04 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 6:51 Uladzimir Bely
2023-01-04 8:20 ` Jan Kiszka
2023-01-04 13:16 ` Henning Schild
2023-01-04 8:28 ` Henning Schild [this message]
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=20230104092847.27e284f6@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.de \
/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