Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Tim Orling" <timothy.t.orling@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] recipetool fixes
Date: Fri, 10 Jul 2020 20:48:06 -0700	[thread overview]
Message-ID: <cover.1594438523.git.timothy.t.orling@linux.intel.com> (raw)

There are some issues with the existing recipetool codebase:
(1) It is _impossible_ to insert the AUTHOR variable in the recommended
    location [1]. And the BBCLASSEXTEND variable is also missing from
    the list (although inserting that in the recommended location is
    trivial).
(2) Several regex patterns are missing the r' prefix, which leads tools
    like pylint/autopep8 to throw warnings because the regex patterns...
    are not identified as regex patterns.

[1] http://www.openembedded.org/wiki/Styleguide

The following changes since commit b3c96103a5063eeefb0c537227eab3f77616b9c0:

  libnl: Extend for native/nativesdk (2020-07-08 10:56:11 +0100)

are available in the Git repository at:

  git://git.openembedded.org/openembedded-core-contrib timo/oe-recipetool-fixes
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=timo/oe-recipetool-fixes

Tim Orling (2):
  lib/oe/recipeutils.py: add AUTHOR; BBCLASSEXTEND
  scripts/lib/recipetool/create.py: fix regex strings

 meta/lib/oe/recipeutils.py       |  2 +-
 scripts/lib/recipetool/create.py | 10 +++++-----
 2 files changed, 6 insertions(+), 6 deletions(-)

-- 
2.24.0


             reply	other threads:[~2020-07-11  3:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11  3:48 Tim Orling [this message]
2020-07-11  3:48 ` [PATCH 1/2] lib/oe/recipeutils.py: add AUTHOR; BBCLASSEXTEND Tim Orling
2020-07-11  3:48 ` [PATCH 2/2] scripts/lib/recipetool/create.py: fix regex strings Tim Orling
  -- strict thread matches above, loose matches on Subject: below --
2020-07-11  3:23 [PATCH 0/2] recipetool fixes Tim Orling

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=cover.1594438523.git.timothy.t.orling@linux.intel.com \
    --to=timothy.t.orling@linux.intel.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox