From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v3] dpkg: sbuild allows extra arguments via DPKG_SBUILD_EXTRA_ARGS v3
Date: Wed, 01 Feb 2023 09:19:08 +0300 [thread overview]
Message-ID: <2022580.YKUYFuaPT4@hp> (raw)
In-Reply-To: <20230125164227.1448218-1-roberto.foglietta@linuxteam.org>
In mail from Wednesday, 25 January 2023 19:42:27 +03 user
roberto.foglietta@linuxteam.org wrote:
> From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
>
> Sometimes it is necessary to add some extra commands or arguments for
> the sbuild process which produces customs packages but creating a class
> into an upper layer just for this will create difficulties in managing
> the updates from the upstream project.
>
> So, this patch allows setting extra parameters via this variable:
>
> DPKG_SBUILD_EXTRA_ARGS
>
> v.2: just a single variable and not anymore two of them
>
> v.3: the variable is set in the middle, just in case order matters, it
> is the last of 'setup chroot' and the first of 'final build' commands
>
> Signed-off-by: Roberto A. Foglietta <roberto.foglietta@gmail.com>
> ---
> v.2: just a single variable and not anymore two of them
>
> v.3: the variable is set in the middle, just in case order matters, it
> is the last of 'setup chroot' and the first of 'final build' commands
>
> meta/classes/dpkg.bbclass | 3 +++
> 1 file changed, 3 insertions(+)
>
Applied to next (with cleaned version history in commit message), thanks.
next prev parent reply other threads:[~2023-02-01 6:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 16:42 roberto.foglietta
2023-02-01 6:19 ` Uladzimir Bely [this message]
2023-02-01 14:46 ` Roberto A. Foglietta
2023-02-01 14:47 ` Jan Kiszka
2023-02-01 15:30 ` Roberto A. Foglietta
2023-02-01 15:40 ` Jan Kiszka
2023-02-01 15:48 ` Roberto A. Foglietta
2023-02-01 19:02 ` Jan Kiszka
2023-02-02 9:04 ` Uladzimir Bely
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=2022580.YKUYFuaPT4@hp \
--to=ubely@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