All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: meta-oe and yocto-check-layer
Date: Tue, 25 Sep 2018 09:03:32 +1200	[thread overview]
Message-ID: <2100274.NFsm02Mysr@localhost.localdomain> (raw)
In-Reply-To: <CAP71Wjxwv3i2=UtbzNai79h-f83xcL6G1R8+kY-C-jA==VFy9Q@mail.gmail.com>

Hi Nicolas,

On Monday, 24 September 2018 10:05:02 PM NZST Nicolas Dechesne wrote:
> hi Armin, Paul, Richard,
> 
> I was looking at getting the compliance report for meta-oe (sumo
> branch), and I have found a few issues.
> 
> * in meta-openembedded/sumo, grpc is in meta-oe layer, while it
> depends on meta-networking (c-ares). It was fixes in master, with
> 251878e8b6b9 (grpc: move it from oe to networking layer), so I think
> this fix needs to be backported to sumo as well if we want the YP 2.0
> compliance script to even work. If agreed, once merged, please let me
> know so that I can try again to generate a compliance report.

Is it appropriate to make such moves in a stable branch? I wouldn't have 
thought so.
 
> * in order to run the compliance report, i locally added
> networking-layer in meta-oe/conf/layer.conf, and it creates a
> dependency loop since meta-oe <-> meta-networking. I found out that
> yocto-check-layer doesn't like that too much, and brutally fails. The
> following patch makes yocto-check-layer work again even with
> dependency loop. I am going to do a few more tests and send that over
> as a patch.
> 
> diff --git a/scripts/lib/checklayer/__init__.py
> b/scripts/lib/checklayer/__init__.py
> index 2618416fab..0cc9bf3b6d 100644
> --- a/scripts/lib/checklayer/__init__.py
> +++ b/scripts/lib/checklayer/__init__.py
> @@ -151,11 +151,21 @@ def add_layer_dependencies(bblayersconf, layer,
> layers, logger):
>          logger.debug('Processing dependencies %s for layer %s.' % \
>                      (depends, layer['name']))
> 
> +        # To avoid never ending recursion, we keep track of layers while
> +        # they are being processed in this 'static' attribute.
> +        if not hasattr(recurse_dependencies, "layers"):
> +            recurse_dependencies.layers = []
> +
>          for depend in depends.split():
>              # core (oe-core) is suppose to be provided
>              if depend == 'core':
>                  continue
> 
> +            if depend in recurse_dependencies.layers:
> +                continue
> +
> +            recurse_dependencies.layers.append(depend)
> +
>              layer_depend = _find_layer_depends(depend, layers)
>              if not layer_depend:
>                  logger.error('Layer %s depends on %s and isn\'t found.' % \

Patch looks reasonable to me FWIW.

Cheers,
Paul


-- 

Paul Eggleton
Intel Open Source Technology Centre




  reply	other threads:[~2018-09-24 21:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24 10:05 meta-oe and yocto-check-layer Nicolas Dechesne
2018-09-24 21:03 ` Paul Eggleton [this message]
2018-09-24 21:51   ` akuster808
2018-09-25  6:59     ` Nicolas Dechesne
2018-09-25  9:43       ` Nicolas Dechesne
2018-09-25 10:19         ` Paul Eggleton
2018-09-25 10:24         ` Martin Jansa
2018-09-25 10:29           ` Martin Jansa
2018-09-25 13:05             ` Nicolas Dechesne
2018-09-25 17:10               ` Martin Jansa
2018-09-25 17:16                 ` Nicolas Dechesne
2018-09-25 17:19                   ` Khem Raj
2018-09-25 17:20                   ` Martin Jansa
2018-09-25 16:47         ` Khem Raj

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=2100274.NFsm02Mysr@localhost.localdomain \
    --to=paul.eggleton@linux.intel.com \
    --cc=nicolas.dechesne@linaro.org \
    --cc=openembedded-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.