public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [PATCH] Fix spec file USE flag parsing
Date: Wed, 14 Oct 2020 10:50:41 -0700	[thread overview]
Message-ID: <CAEdQ38F22EUQCmsBiK_Z=g1L3dF6quNkGDmt1AHATmmib_xctQ@mail.gmail.com> (raw)
In-Reply-To: <194d64866a4f7f8f9e5e89ad2d23e6e1b3b7a54a.camel@rohde-schwarz.com>

On Wed, Oct 14, 2020 at 6:38 AM Felix Bier <Felix.Bier@rohde-schwarz.com> wrote:
>
> In stagebase, the set_use function applies .split() to the use flags
> passed from the spec file, if the value is a string. However, the
> result is immediately overwritten after the if-statement. Therefore the
> .split() is ineffectual.
>
> This results in self.settings["use"] holding a string,
> which is then regarded as a list of characters in write_make_conf.
> This fix ensures that the result of the split is not overwritten
> (matching the similar code in set_catalyst_use).
>
> For example, setting "stage4/use: abc" in a spec file results
> in USE="a b c ..." in the generated make.conf.
> With this fix, the generated make.conf contains the expected
> USE="abc ...".
> ---
>  catalyst/base/stagebase.py | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/catalyst/base/stagebase.py b/catalyst/base/stagebase.py
> index df1cb844..2e313bd8 100644
> --- a/catalyst/base/stagebase.py
> +++ b/catalyst/base/stagebase.py
> @@ -512,7 +512,8 @@ class StageBase(TargetBase, ClearBase, GenBase):
>          if use in self.settings:
>              if isinstance(self.settings[use], str):
>                  self.settings["use"] = self.settings[use].split()
> -            self.settings["use"] = self.settings[use]
> +            else:
> +                self.settings["use"] = self.settings[use]
>              del self.settings[use]
>          else:
>              self.settings["use"] = []
> --
> 2.28.0

Thanks, this indeed looks broken. It was broken by b30dd97d672d by the
looks of it.

Reviewed-by: Matt Turner <mattst88@gentoo.org>

and committed.


      reply	other threads:[~2020-10-14 17:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 13:38 [gentoo-catalyst] [PATCH] Fix spec file USE flag parsing Felix Bier
2020-10-14 17:50 ` Matt Turner [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='CAEdQ38F22EUQCmsBiK_Z=g1L3dF6quNkGDmt1AHATmmib_xctQ@mail.gmail.com' \
    --to=mattst88@gentoo.org \
    --cc=gentoo-catalyst@lists.gentoo.org \
    /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