public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/5] ccache: fix dirs creation
Date: Tue, 20 Dec 2022 02:39:20 +0000	[thread overview]
Message-ID: <f8ff87c06b29eefa2f31c27e2299aa19a036d14e.camel@siemens.com> (raw)
In-Reply-To: <20221219142933.12437-2-amikan@ilbers.de>

On Mon, 2022-12-19 at 17:29 +0300, Anton Mikanovich wrote:
> Create ccache debug directory only if CCACHE_DEBUG is enabled.
> Also restore CCACHE_DIR creation if not exist.
> 
> Fixes 7956c4c ("add flag to enable ccache debug mode")

The reason I implemented it like that was to avoid conditional
execution paths. All these paths need testing and the value of not
creating the ${CCACHE_DIR}/debug is very little (or is there a
technical reason why the debug folder should not be there?).

> 
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
>  meta/classes/buildchroot.bbclass | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/classes/buildchroot.bbclass
> b/meta/classes/buildchroot.bbclass
> index b4ff2886..72eb80bc 100644
> --- a/meta/classes/buildchroot.bbclass
> +++ b/meta/classes/buildchroot.bbclass
> @@ -25,7 +25,10 @@ MOUNT_LOCKFILE = "${BUILDCHROOT_DIR}.lock"
>  
>  buildchroot_do_mounts() {
>      if [ "${USE_CCACHE}" = "1" ]; then
> -        mkdir -p ${CCACHE_DIR}/debug
> +        mkdir -p ${CCACHE_DIR}
> +        if [ "${CCACHE_DEBUG}" = "1" ]; then
> +            mkdir -p ${CCACHE_DIR}/debug

As we touch this code now, please also put the paths in quotes to make
sure directories with spaces are handled correctly.

Felix

> +        fi
>      fi
>  
>      sudo -s <<'EOSUDO'
> -- 
> 2.17.1
> 


  parent reply	other threads:[~2022-12-20  2:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 14:29 [PATCH 0/5] Fix ccache issues Anton Mikanovich
2022-12-19 14:29 ` [PATCH 1/5] ccache: fix dirs creation Anton Mikanovich
2022-12-19 15:21   ` Henning Schild
2023-02-08  8:01     ` Anton Mikanovich
2022-12-20  2:39   ` Moessbauer, Felix [this message]
2022-12-19 14:29 ` [PATCH 2/5] ccache: fix CCACHE_DIR owner for sbuild Anton Mikanovich
2022-12-19 15:23   ` Henning Schild
2022-12-20  2:40     ` Moessbauer, Felix
2023-01-12 10:00   ` Moessbauer, Felix
2023-02-08  8:15     ` Anton Mikanovich
2022-12-19 14:29 ` [PATCH 3/5] dpkg-base: remove deprecated code Anton Mikanovich
2022-12-19 14:29 ` [PATCH 4/5] meta: unify cross selection Anton Mikanovich
2022-12-20  2:49   ` Moessbauer, Felix
2022-12-19 14:29 ` [PATCH 5/5] ccache: separate cache based on cross compile Anton Mikanovich
2022-12-20  2:59   ` Moessbauer, Felix
2023-01-11  6:49 ` [PATCH 0/5] Fix ccache issues 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=f8ff87c06b29eefa2f31c27e2299aa19a036d14e.camel@siemens.com \
    --to=felix.moessbauer@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