From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: [PATCH] sanity.bbclass: grammar/typo fixes re: Python install
Date: Thu, 12 May 2022 04:45:57 -0400 (EDT) [thread overview]
Message-ID: <49c3457d-897a-cca5-ec91-c442be9ea18@crashcourse.ca> (raw)
Clean up various spelling/grammar oopsies in a small section of
sanity.bbclass.
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
---
diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
index b416918013..491a3bac6f 100644
--- a/meta/classes/sanity.bbclass
+++ b/meta/classes/sanity.bbclass
@@ -631,11 +631,14 @@ def check_sanity_sstate_dir_change(sstate_dir, data):
def check_sanity_version_change(status, d):
# Sanity checks to be done when SANITY_VERSION or NATIVELSBSTRING changes
# In other words, these tests run once in a given build directory and then
- # never again until the sanity version or host distrubution id/version changes.
+ # never again until the sanity version or host distribution id/version changes.
+
+ # Verify that the python install is complete. Examples that are often removed in
+ # minimal installations:
+ #
+ # glib-2.0-native requires xml.parsers.expat
+ # icu requires distutils.sysconfig
- # Check the python install is complete. Examples that are often removed in
- # minimal installations: glib-2.0-natives requries # xml.parsers.expat and icu
- # requires distutils.sysconfig.
try:
import xml.parsers.expat
import distutils.sysconfig
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2022-05-12 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 8:45 Robert P. J. Day [this message]
2022-05-16 7:32 ` [OE-core] [PATCH] sanity.bbclass: grammar/typo fixes re: Python install Luca Ceresoli
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=49c3457d-897a-cca5-ec91-c442be9ea18@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--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