All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [RFC PATCH 2/2] bitbake-layers: handle skipped recipes
Date: Thu, 02 Jun 2011 13:03:45 -0700	[thread overview]
Message-ID: <1307045035.2050.16.camel@scimitar> (raw)
In-Reply-To: <6dda84cc0d5c63c7b09df0631d9082cbbcd2bd2f.1306947210.git.paul.eggleton@linux.intel.com>

On Wed, 2011-06-01 at 18:26 +0100, Paul Eggleton wrote:
> Report bbappends correctly for skipped recipes instead of reporting the
> bbappends as not having any matching recipe.
> 
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>

Cool! I know this depends on the 1st patch but

Signed-off-by: Joshua Lock <josh@linux.intel.com>

> ---
>  bitbake/bin/bitbake-layers |   24 +++++++++++++++++++-----
>  1 files changed, 19 insertions(+), 5 deletions(-)
> 
> diff --git a/bitbake/bin/bitbake-layers b/bitbake/bin/bitbake-layers
> index b6106cd..c58aee3 100755
> --- a/bitbake/bin/bitbake-layers
> +++ b/bitbake/bin/bitbake-layers
> @@ -81,6 +81,8 @@ class Commands(cmd.Cmd):
>          for pn in self.cooker_data.pkg_pn:
>              self.show_appends_for_pn(pn)
>  
> +        self.show_appends_for_skipped()
> +
>          self.show_appends_with_no_recipes()
>  
>      def show_appends_for_pn(self, pn):
> @@ -92,17 +94,27 @@ class Commands(cmd.Cmd):
>                                               self.cooker_data.pkg_pn)
>          best_filename = os.path.basename(best[3])
>  
> +        self.show_appends_output(filenames, best_filename)
> +
> +    def show_appends_for_skipped(self):
> +        filenames = [os.path.basename(f)
> +                    for f in self.cooker.skiplist.iterkeys()]
> +        self.show_appends_output(filenames, None, " (skipped)")
> +
> +    def show_appends_output(self, filenames, best_filename, name_suffix = ''):
>          appended, missing = self.get_appends_for_files(filenames)
>          if appended:
>              for basename, appends in appended:
> -                logger.info('%s:', basename)
> +                logger.info('%s%s:', basename, name_suffix)
>                  for append in appends:
>                      logger.info('  %s', append)
>  
> -            if best_filename in missing:
> -                logger.warn('%s: missing append for preferred version',
> -                            best_filename)
> -                self.returncode |= 1
> +            if best_filename:
> +                if best_filename in missing:
> +                    logger.warn('%s: missing append for preferred version',
> +                                best_filename)
> +                    self.returncode |= 1
> +
>  
>      def get_appends_for_files(self, filenames):
>          appended, notappended = set(), set()
> @@ -122,6 +134,8 @@ class Commands(cmd.Cmd):
>      def show_appends_with_no_recipes(self):
>          recipes = set(os.path.basename(f)
>                        for f in self.cooker_data.pkg_fn.iterkeys())
> +        recipes |= set(os.path.basename(f)
> +                      for f in self.cooker.skiplist.iterkeys())
>          appended_recipes = self.cooker_data.appends.iterkeys()
>          appends_without_recipes = [self.cooker_data.appends[recipe]
>                                     for recipe in appended_recipes

-- 
Joshua Lock
        Yocto Build System Monkey
        Intel Open Source Technology Centre




      reply	other threads:[~2011-06-02 20:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 17:26 [RFC PATCH 0/2] skipped recipe handling Paul Eggleton
2011-06-01 17:26 ` [RFC PATCH 1/2] bitbake: track skipped packages Paul Eggleton
2011-06-02 20:01   ` Joshua Lock
2011-06-03  9:51     ` Paul Eggleton
2011-06-03 16:38       ` Joshua Lock
2011-06-01 17:26 ` [RFC PATCH 2/2] bitbake-layers: handle skipped recipes Paul Eggleton
2011-06-02 20:03   ` Joshua Lock [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=1307045035.2050.16.camel@scimitar \
    --to=josh@linux.intel.com \
    --cc=bitbake-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.