public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Felix Moessbauer <felix.moessbauer@siemens.com>
Cc: isar-users@googlegroups.com, florian.bezdeka@siemens.com
Subject: Re: [PATCH] override HOME to isolate sbuild configuration
Date: Tue, 20 Sep 2022 12:58:32 +0200	[thread overview]
Message-ID: <20220920125832.55602ed6@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20220920092654.1314022-1-felix.moessbauer@siemens.com>

Am Tue, 20 Sep 2022 11:26:54 +0200
schrieb Felix Moessbauer <felix.moessbauer@siemens.com>:

> This patch sets the HOME env var to the package build path
> to avoid conflicts with an existing .sbuildrc configuration
> in the users homedir.
> 
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
>  meta/classes/dpkg.bbclass | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
> index c92ea7db..70f8e772 100644
> --- a/meta/classes/dpkg.bbclass
> +++ b/meta/classes/dpkg.bbclass
> @@ -17,6 +17,8 @@ dpkg_runbuild() {
>      E="${@ isar_export_ccache(d)}"
>      export DEB_BUILD_OPTIONS="${@ isar_deb_build_options(d)}"
>      export PARALLEL_MAKE="${PARALLEL_MAKE}"
> +    # override HOME to not interfer with users .sbuildrc
> +    export HOME="${PP}"

This is not kas, maybe people want that from isar. And if they do not
want it they can use kas.

I would bbwarn on -f ~/.sbuildrc, setting HOME to something else is
pretty heavy and can have all sorts of fun side-effects.

Henning
 
>      rm -f ${SBUILD_CONFIG}
>  


  reply	other threads:[~2022-09-20 10:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20  9:26 Felix Moessbauer
2022-09-20 10:58 ` Henning Schild [this message]
2022-09-20 11:22   ` Moessbauer, Felix
2022-09-23  9:17     ` Anton Mikanovich
2022-09-25  8:13       ` Moessbauer, Felix

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=20220920125832.55602ed6@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=florian.bezdeka@siemens.com \
    --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