All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Lehtonen <markus.lehtonen@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] devtool: include bbappends in recipe parsing
Date: Wed, 22 Apr 2015 16:27:05 +0300	[thread overview]
Message-ID: <1429709225.5183.13.camel@linux.intel.com> (raw)
In-Reply-To: <2243141.uRBUZPtYeh@peggleto-mobl.ger.corp.intel.com>

Hi,


On Tue, 2015-04-21 at 17:42 +0100, Paul Eggleton wrote:
> On Tuesday 21 April 2015 17:50:43 Markus Lehtonen wrote:
> > In order to get correct metadata, SRCREV for example.
> > 
> > Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
> > ---
> >  meta/lib/oe/recipeutils.py      |  6 +++---
> >  scripts/lib/devtool/standard.py | 32 +++++++++++++++++++-------------
> >  2 files changed, 22 insertions(+), 16 deletions(-)
> > 
> > diff --git a/meta/lib/oe/recipeutils.py b/meta/lib/oe/recipeutils.py
> > index 159a103..09bd7fd 100644
> > --- a/meta/lib/oe/recipeutils.py
> > +++ b/meta/lib/oe/recipeutils.py
> > @@ -44,10 +44,10 @@ def get_unavailable_reasons(cooker, pn):
> >      return taskdata.get_reasons(pn)
> > 
> > 
> > -def parse_recipe(fn, d):
> > +def parse_recipe(fn, appends, d):
> >      """Parse an individual recipe"""
> >      import bb.cache
> > -    envdata = bb.cache.Cache.loadDataFull(fn, [], d)
> > +    envdata = bb.cache.Cache.loadDataFull(fn, appends, d)
> >      return envdata
> > 
> > 
> > @@ -55,7 +55,7 @@ def get_var_files(fn, varlist, d):
> >      """Find the file in which each of a list of variables is set.
> >      Note: requires variable history to be enabled when parsing.
> >      """
> > -    envdata = parse_recipe(fn, d)
> > +    envdata = parse_recipe(fn, [], d)
> >      varfiles = {}
> >      for v in varlist:
> >          history = envdata.varhistory.variable(v)
> > diff --git a/scripts/lib/devtool/standard.py
> > b/scripts/lib/devtool/standard.py index d5ded2f..96e3bdb 100644
> > --- a/scripts/lib/devtool/standard.py
> > +++ b/scripts/lib/devtool/standard.py
> > @@ -130,18 +130,26 @@ def _get_recipe_file(cooker, pn):
> >              logger.error("Unable to find any recipe file matching %s" % pn)
> > return recipefile
> > 
> > +def _parse_recipe(tinfoil, pn, appends):
> > +    """Parse recipe of a package"""
> > +    import oe.recipeutils
> > +    recipefile = _get_recipe_file(tinfoil.cooker, pn)
> > +    if not recipefile:
> > +        # Error already logged
> > +        return None
> > +    if appends:
> > +        append_files =
> > tinfoil.cooker.collection.get_file_appends(recipefile) +    return
> > oe.recipeutils.parse_recipe(recipefile, append_files,
> > +                                       tinfoil.config_data)
> > 
> >  def extract(args, config, basepath, workspace):
> >      import bb
> > -    import oe.recipeutils
> > 
> >      tinfoil = setup_tinfoil()
> > 
> > -    recipefile = _get_recipe_file(tinfoil.cooker, args.recipename)
> > -    if not recipefile:
> > -        # Error already logged
> > +    rd = _parse_recipe(tinfoil, args.recipename, True)
> > +    if not rd:
> >          return -1
> > -    rd = oe.recipeutils.parse_recipe(recipefile, tinfoil.config_data)
> > 
> >      srctree = os.path.abspath(args.srctree)
> >      initial_rev = _extract_source(srctree, args.keep_temp, args.branch, rd)
> > @@ -327,11 +335,10 @@ def modify(args, config, basepath, workspace):
> > 
> >      tinfoil = setup_tinfoil()
> > 
> > -    recipefile = _get_recipe_file(tinfoil.cooker, args.recipename)
> > -    if not recipefile:
> > -        # Error already logged
> > +    rd = _parse_recipe(tinfoil, args.recipename, True)
> > +    if not rd:
> >          return -1
> > -    rd = oe.recipeutils.parse_recipe(recipefile, tinfoil.config_data)
> > +    recipefile = rd.getVar('FILE', True)
> > 
> >      if not _check_compatible_recipe(args.recipename, rd):
> >          return -1
> > @@ -418,11 +425,10 @@ def update_recipe(args, config, basepath, workspace):
> >      from oe.patch import GitApplyTree
> >      import oe.recipeutils
> > 
> > -    recipefile = _get_recipe_file(tinfoil.cooker, args.recipename)
> > -    if not recipefile:
> > -        # Error already logged
> > +    rd = _parse_recipe(tinfoil, args.recipename, True)
> > +    if not rd:
> >          return -1
> > -    rd = oe.recipeutils.parse_recipe(recipefile, tinfoil.config_data)
> > +    recipefile = rd.getVar('FILE', True)
> > 
> >      orig_src_uri = rd.getVar('SRC_URI', False) or ''
> >      if args.mode == 'auto':
> 
> I ran the oe-selftest tests and unfortunately this appears to cause a 
> regression - you can see the test failure by running:
> 
> oe-selftest --run-tests devtool.DevtoolTests.test_devtool_update_recipe_git
> 
> I suspect this might be because with this patch we'd be seeing the bbappends 
> within the workspace layer, which might tangle things up.

Good point, I'll post an updated patch.

However, seems that the tests got already broken earlier, even before my
patch. I'll send another patch to fix the tests.

Thanks,
  Markus





      reply	other threads:[~2015-04-22 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 14:50 [PATCH] devtool: include bbappends in recipe parsing Markus Lehtonen
2015-04-21 16:42 ` Paul Eggleton
2015-04-22 13:27   ` Markus Lehtonen [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=1429709225.5183.13.camel@linux.intel.com \
    --to=markus.lehtonen@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.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 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.