followup to previous post ... with master oe-core, i did:
* MACHINE = qemuarm64
* core-image-minimal
with only customization:
INIT_MANAGER = "systemd"
the end result was a bootable QEMU image which had the executable
/sbin/nologin, but a number of systemd-related user accounts with
e-utils-syslog = ""
# Blacklist busybox
PNBLACKLIST[busybox] = "Don't build this"
i ask since a colleague just asked me how to do exactly that --
prevent any trace of busybox being used in the final image.
rday
--
=============
hat would be just
ducky.
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http
On Sun, 19 Apr 2020, Richard Purdie wrote:
> On Sat, 2020-04-18 at 18:17 -0400, Robert P. J. Day wrote:
> > that actually matches with what i concluded -- BDIR is dead and
> > gone, but i realized that BITBAKEDIR could still be useful, even
> > if it's currently undocum
On Sat, 18 Apr 2020, Christopher Larson wrote:
> I don’t think this is out of date. It’s allowing the user to specify
> the path to bitbake (which I’ve done in unusual layouts or just to
> be explicit), falling back to either under OEROOT (poky-style) or in
> its parent (more typical).
>
> It’s
On Sat, 18 Apr 2020, Christopher Larson wrote:
> On Apr 18, 2020, 1:10 PM -0700, Robert P. J. Day ,
> wrote:
> On Sat, 18 Apr 2020, Peter Kjellerstedt wrote:
>
> -Original Message-
> From: openembedded-core@list
On Sat, 18 Apr 2020, Peter Kjellerstedt wrote:
> > -Original Message-
> > From: openembedded-core@lists.openembedded.org > c...@lists.openembedded.org> On Behalf Of Robert P. J. Day
> > Sent: den 18 april 2020 19:24
> > To: chris.lapla...@agilent.com
&g
On Sat, 18 Apr 2020, Peter Kjellerstedt wrote:
> > -Original Message-
> > From: openembedded-core@lists.openembedded.org > c...@lists.openembedded.org> On Behalf Of Robert P. J. Day
> > Sent: den 18 april 2020 19:24
> > To: chris.lapla...@agilent.com
&g
On Sat, 18 Apr 2020, chris.lapla...@agilent.com wrote:
> > i know that -- in fact, it's the only way i use it -- the question
> > is the purpose for checking if $BDIR is zero length first. that is,
> > under what circumstances could it *not* be? even invoking the way you
> > demonstrate, that
On Sat, 18 Apr 2020, Richard Purdie wrote:
> On Sat, 2020-04-18 at 12:04 -0400, Robert P. J. Day wrote:
> > perusing the OE init scripts, and noticed this in
> > oe-buildenv-internal, line 42:
> >
> > if [ -z "$BDIR" ]; then
> > if [ -z "$
perusing the OE init scripts, and noticed this in
oe-buildenv-internal, line 42:
if [ -z "$BDIR" ]; then
if [ -z "$1" ]; then
BDIR="build"
else
BDIR="$1"
... snip ...
i'm curious ... under what circumstances would BDIR *not* be unset
(or not be the empty string)
On Fri, 17 Apr 2020, Alexander Kanavin wrote:
> ptest-pkgs is complementary; it pulls in ptests only for those
> packages that are explicitly included in the image. (similar to how
> dev-pkgs or doc-pkgs work).
>
> Generally, it is not recommended to use ptest-pkgs as you never know
> what you
as a demo of how ptest works, i used the current master branch of
poky, MACHINE=qemuarm64, built core-image-minimal, and selected to
install ptests with:
DISTRO_FEATURES_append = " ptest"
EXTRA_IMAGE_FEATURES += "ptest-pkgs"
following the directions in the dev manual. but when it was all
colleague just pointed out that, in a new core-image-minimal, the
base-passwd recipe loads up /etc/passwd (based on initial
passwd.master file) with various accounts that really don't merit a
login shell of /bin/sh:
...
daemon:*:1:1:daemon:/usr/sbin:/bin/sh
bin:*:2:2:bin:/bin:/bin/sh
was documenting, you know, stuff and noticed that when building for
MACHINE = qemux86-64, the variable IMAGE_CLASSES contained the entry
for qemuboot twice:
IMAGE_CLASSES=" qemuboot qemuboot license_image"
easy to see why ... those machine conf files both contain:
require
was looking to expand on the whole "rm_work" documentation, only to
discover i was profoundly ignorant of some of its features (don't say
it :-).
so, first, there's the basic stuff (which is already in the YP
documentation):
INHERIT += "rm_work"
RM_WORK_EXCLUDE += "pkg1 pkg2 ..."
then
i note that, way back in YP ref manual, migration to YP 2.3, we
read:
"The SSTATEPOSTINSTFUNCS variable itself is now deprecated in favor of
the do_populate_sysroot[postfuncs] task. Consequently, if you do still
have any function or functions that need to be called after the
sysroot component
On Tue, 7 Apr 2020, Alexander Kanavin wrote:
> These run
> - at image creation time in the context of package manager
> (dnf/apt/opkg) installing packages into the image rootfs
> directory. The code that executes the package manager specifically
> exports $D into the environment before
On Tue, 7 Apr 2020, Alexander Kanavin wrote:
> These run
> - at image creation time in the context of package manager
> (dnf/apt/opkg) installing packages into the image rootfs
> directory. The code that executes the package manager specifically
> exports $D into the environment before
On Tue, 7 Apr 2020, Alexander Kanavin wrote:
> These run
> - at image creation time in the context of package manager
> (dnf/apt/opkg) installing packages into the image rootfs
> directory. The code that executes the package manager specifically
> exports $D into the environment before
first time looking closely at pkg_postinst_* routines, so can
someone clarify the use of "$D" in those routines? at the moment, i'm
*guessing* that those routines need to be able to run in two different
contexts (but i could be wrong):
1) at image creation time
2) at later package
wanted to expand on the explanation of post-install scripts using
examples out of OE/YP layers, and ran across this oddity in
meta-openembedded/meta-networking, in quagga.inc.
here's what's at line 146:
pkg_postinst_${PN} () {
if ${@bb.utils.contains('DISTRO_FEATURES', 'systemd sysvinit',
On Fri, 20 Mar 2020, Adrian Bunk wrote:
> On Fri, Mar 20, 2020 at 07:04:05AM -0400, Robert P. J. Day wrote:
> >...
> > in this current situation, it turns out that that sample conf file
> > just happens to be appropriate,
> >...
>
> I'd guess you are wr
.
>
> rday
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
--
==
got into a discussion yesterday about the "cleanest" way to design a
.bbappend file to install a package's configuration file, so i'm
curious about best practices, and here's an example. (and i'm asking
as it looks like this will be an issue for a number of recipes i'm
looking at.)
current
looking for a "best practises" suggestion ... currently working with
a layer based on morty (2.2), migrating it to thud (2.6) and i notice
that there are a *lot* of .bb recipe files in the morty layer that
did not exist in any of the official OE/YP layers in morty, so they
were added by
On Sun, 1 Mar 2020, Robert P. J. Day wrote:
>
> occasionally, i run across an existing bbappend file which contains
>
> FILESEXTRAPATHS_append := ...
>
> and that makes me nervous as i don't see the rationale in *appending*
> to that variable in a bbappend file -- seems
EXTRAPATHS? that just seems counter-productive, but maybe i'm
missing something.
rday
--
========
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.c
still meant to be used?
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn:
P
2.3 talks only about systemd.
thoughts?
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter:
On Sat, 22 Feb 2020, Adrian Bunk wrote:
> On Sat, Feb 22, 2020 at 04:07:56PM -0500, Robert P. J. Day wrote:
> > On Sat, 22 Feb 2020, Alexander Kanavin wrote:
> >
> > > BBMASK?
> >
> > BTW, that will work for me in this situation but is there a way to
>
On Sat, 22 Feb 2020, Alexander Kanavin wrote:
> BBMASK?
BTW, that will work for me in this situation but is there a way to
not have to enumerate all the recipes to ignore, and just say, "don't
look at anything that is not related to building core-image-minimal?"
*that* would be seriously
On Sat, 22 Feb 2020, Alexander Kanavin wrote:
> BBMASK?
thank you. i knew there was something, i was just drawing a blank
and i can't remember the last time i needed to do that.
rday
--
___
Openembedded-core mailing list
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
nd so on, and so on?
would this not be equivalent to just writing:
COMPATIBLE_MACHINE = "genericx86|genericx86-64|edgerouter|..."
(or possibly with += depending on what else is going on.)
is there something different by using those individual assignments?
rday
--
===============
(note: when i finally learn python, i'll be able to RTFS and figure
out stuff like this without assistance. until then ...)
was going to enhance the explanation of PREFERRED_PROVIDER in the
docs, until i realized i don't understand it completely.
first, if there is a recipe named, say,
Corrections:
- environment
- accommodate
- conversion
- compatible
Signed-off-by: Robert P. J. Day
---
diff --git a/meta/classes/testimage.bbclass b/meta/classes/testimage.bbclass
index 75f0f2c3e3..359f240b0b 100644
--- a/meta/classes/testimage.bbclass
+++ b/meta/classes
On Sun, 16 Feb 2020, Peter Kjellerstedt wrote:
> >
> >
> > /
> > -@@ -259,38 +263,39 @@ cpu-state-varible M.x86.mode. There are several
> > potential states:
> > +@@ -259,38 +263,39 @@ cpu-state-variable M.x86.mode.
ean.
rday
--
========
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjda
i remember wondering about this a long time ago, then forgot
about it, but in some of the poky linux-yocto kernel .bbappend files,
there are sets of individual COMPATIBLE_MACHINE settings:
COMPATIBLE_MACHINE_genericx86 = "genericx86"
COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
Corrections:
- environment
- variable
- accommodate
- conversion
- compatible
Signed-off-by: Robert P. J. Day
---
diff --git a/meta/classes/testimage.bbclass b/meta/classes/testimage.bbclass
index 75f0f2c3e3..359f240b0b 100644
--- a/meta/classes/testimage.bbclass
+++ b/meta/classes
On Sat, 15 Feb 2020, Robert P. J. Day wrote:
... snip ...
> second, the only example of that feature in all of oe-core is
> cdrtools-native_3.01.bb, which contains:
>
> PV = "3.01a31+really3.01"
> REALPV = "3.01"
>
> but that doesn't seem to matc
digging through YP dev tasks manual, section 3.3.18, "Properly
Versioning Pre-Release Recipes", and the admittedly minimal usage of
that feature in oe-core doesn't really seem to bolster the
description.
in YP manual, example for irssi recipe:
REALPV = "0.8.16-rc1"
PV =
"swuashfs"?
rday
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
was documenting the use of [EXTRA_]IMAGE_FEATURES, and noticed that
while the oe-core layer defines a related feature:
core-image.bbclass:FEATURE_PACKAGES_hwcodecs = "${MACHINE_HWCODECS}"
core-image.bbclass:MACHINE_HWCODECS ??= ""
i see no actual usage of that variable in oe-core (the
i have some scripts that wander the layers and look for possible
typos, and i ran across this:
meta/lib/oeqa/selftest/cases/incompatible_lic.py:IMAGE_INSTALL_append = "bash"
should that value have a leading space or not? i'll let someone else
deal with that if it needs fixing.
rday
--
Signed-off-by: Robert P. J. Day
---
that's the only example of that i can see.
diff --git a/meta/classes/icecc.bbclass b/meta/classes/icecc.bbclass
index bc3d6f4cc8..d095305ed8 100644
--- a/meta/classes/icecc.bbclass
+++ b/meta/classes/icecc.bbclass
@@ -105,7 +105,7 @@ def
"initramdfs"?
rday
--
========
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.
"pacakge"?
rday
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
rse.ArgumentParser(description='Bashim detector for shell
> fragments in recipes.')
^^ ???
rday
--
================
Robert P. J. Day Ottawa, O
Signed-off-by: Robert P. J. Day <rpj...@crashcourse.ca>
---
diff --git a/meta/lib/oeqa/selftest/cases/layerappend.py
b/meta/lib/oeqa/selftest/cases/layerappend.py
index 9562116..2fd5cdb 100644
--- a/meta/lib/oeqa/selftest/cases/layerappend.py
+++ b/meta/lib/oeqa/selftest/cases/layerapp
son that SRC_URI_append is done correctly in that
first example, but in that weirdly superfluous way using "+=" in the
second example?
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
rity? or what?
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn:
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
the only references i see to the deprecated FILESDIR are historical,
none actually being used. what about just tossing it?
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
algo = "sha1";
};
};
c...@am335x-boneblack.dtb {
description = "0 Linux kernel, FDT blob";
kernel = "kernel@1";
fdt = "f...@am335x-boneblack.dtb";
On Wed, 29 Mar 2017, Richard Purdie wrote:
> On Wed, 2017-03-29 at 05:56 -0400, Robert P. J. Day wrote:
> > On Wed, 29 Mar 2017, Robert P. J. Day wrote:
> >
> > >
> > > again, trying to catch up with new developments, and i want to
> > > make su
On Wed, 29 Mar 2017, Robert P. J. Day wrote:
> again, trying to catch up with new developments, and i want to
> make sure i understand these variables. as i read it (and i could be
> off-base), HOSTTOOLS represents a list of tools that *must* be
> available one way or the other, a
.
apologies for my confusion.
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com
clarify this?
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.lin
ort.
rday
--
========
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com
On Tue, 28 Mar 2017, Peter Kjellerstedt wrote:
> > -Original Message-
> > From: openembedded-core-boun...@lists.openembedded.org
> > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> > Robert P. J. Day
> > Sent: den 28 mars 2017 12:5
machine conf
file and generate *just* those images? or am i missing something here?
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://t
On Tue, 28 Mar 2017, Burton, Ross wrote:
>
> On 28 March 2017 at 11:50, Robert P. J. Day <rpj...@crashcourse.ca> wrote:
> gconf_postinst() {
> -if [ "x$D" != "x" ]; then
> +if [ -n "${D}" ]; then
>
>
> This totally c
On Tue, 28 Mar 2017, Burton, Ross wrote:
>
> On 28 March 2017 at 11:50, Robert P. J. Day <rpj...@crashcourse.ca> wrote:
> gconf_postinst() {
> -if [ "x$D" != "x" ]; then
> +if [ -n "${D}" ]; then
>
>
> This totally c
On Tue, 28 Mar 2017, Peter Kjellerstedt wrote:
> > -Original Message-
> > From: openembedded-core-boun...@lists.openembedded.org
> > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> > Robert P. J. Day
> > Sent: den 28 mars 2017 11:57
For better or worse, two types of cleanup in meta/classes directory:
* Replace old-style 'x${VAR} = x' tests with -n/-z string tests
* Unsplit lines to keep if/then, while/do on same line
Signed-off-by: Robert P. J. Day <rpj...@crashcourse.ca>
---
i realize there are two types of t
On Mon, 27 Mar 2017, Richard Purdie wrote:
> On Sat, 2017-03-25 at 14:03 -0400, Robert P. J. Day wrote:
> > In entire meta/classes/ directory, replace shell tests of the form
> > "if test -? ..." with POSIX tests of the form "if [ -? ...
> >
>
On Mon, 13 Mar 2017, Mark Hatle wrote:
> On 3/11/17 3:57 AM, Robert P. J. Day wrote:
> > On Sat, 11 Mar 2017, Khem Raj wrote:
> >
> >> On 3/11/17 12:30 AM, Robert P. J. Day wrote:
> >>>
> >>> potentially a dumb question, but do the settings
For aesthetic style reasons, use "grep -q" instead of ">/dev/null".
Signed-off-by: Robert P. J. Day <rpj...@crashcourse.ca>
---
diff --git a/meta/classes/autotools.bbclass b/meta/classes/autotools.bbclass
index d494734..ac04a07 100644
--- a/meta/classes/autotoo
efault/dropbear 2>/dev/null ; then
utils.bbclass: if echo "$destpath/" | egrep '^${STAGING_LIBDIR}/' >/dev/null
$
1) can most of those be simplified with "grep -q"?
2) is there any need for "egrep" in that last match?
rday
--
==
In entire meta/classes/ directory, replace shell tests of the form
"if test -? ..." with POSIX tests of the form "if [ -? ...
Signed-off-by: Robert P. J. Day <rpj...@crashcourse.ca>
---
as i cannot abide those silly "if test" constructs, i zipped through
On Thu, 23 Mar 2017, Mark Hatle wrote:
> On 3/22/17 7:02 PM, Robert P. J. Day wrote:
> > On Wed, 22 Mar 2017, Burton, Ross wrote:
> >
> >>
> >> On 22 March 2017 at 10:51, Robert P. J. Day <rpj...@crashcourse.ca> wrote:
> >> from site
to enforce a processing order, but when one has a
numbered series of patches getting up to 20 or 25, that strikes me as
time to collapse all that into larger and more modular and more
meaningful patches.
thoughts?
rday
--
=============
On Wed, 22 Mar 2017, Bruce Ashfield wrote:
>
>
> On Wed, Mar 22, 2017 at 8:24 AM, Robert P. J. Day <rpj...@crashcourse.ca>
> wrote:
>
> proper attributions seem to have been totally lost here ...
>
> On Wed, 22 Mar 2017, Bruce Ashfield wrote:
>
&g
things to happen like the above?
2) regardless of how the developer eventually does it, picking up
those PREFERRED VERSIONS from meta-openstack should require *some*
kind of explicit selection?
thank you kindly.
rday
--
=
whether you use anything from the meta-openstack layer
or not? wouldn't those selections be properly placed elsewhere in the
layer, and not in layer.conf?
rday
--
Robert P. J. Day
On Wed, 22 Mar 2017, Burton, Ross wrote:
>
> On 22 March 2017 at 10:51, Robert P. J. Day <rpj...@crashcourse.ca> wrote:
> from site.conf.sample, the obvious content is things like:
>
> * download dir
> * reference to local (in-house) source mirro
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
86-64 ELF executable, not powerpc.
i'm sure i could tease out how to hack that Makefile, but is there
another recipe with a similar structure i could just steal a Makefile
from?
rday
--
================
Robert P. J. Day
also accel-ppp, but it claims to be currently blacklisted:
http://layers.openembedded.org/layerindex/recipe/2315/
anyway, suggestions for equivalent PPTP servers to poptop? thank you
kindly.
rday
--
===============
otice, and ask about, and i end up looking at it, going, "i haven't
the foggiest idea what the heck that's all about." hence my obsession
with consistency.
--
Robert P. J. Day
ioned earlier
if [ "x${ICE_PATH}" = "x" ] rather than if [ -z "${ICE_PATH}" ]
if [ ! -z "${conf_sign_keyname}" ] ... ?? :-)
none of this is a big deal, but there sure are some historical
holdovers and strangely-chosen constructs.
rday
--
S_IMAGE}" ; then
would it not be equivalent to write that second test as:
[ -n "${INITRAMFS_IMAGE}"]
and so on. what are we allowed to count on?
rday
--
================
Robert P. J. Day O
task for that, or can i just manually "rm" them to
get the same effect?
rday
--
========
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.c
ear.
rday
--
========
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjda
all the threads
together to understand the consequences.
rday
--
====
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twit
U-Boot people are amazingly pedantic in their insistence on proper
spelling of "U-Boot", so humour them.
Signed-off-by: Robert P. J. Day <rpj...@crashcourse.ca>
---
diff --git a/meta/classes/kernel-fitimage.bbclass
b/meta/classes/kernel-fitimage.bbclass
index 1c3b4b7..f9702f8 1
On Sat, 11 Mar 2017, Khem Raj wrote:
> On 3/11/17 12:30 AM, Robert P. J. Day wrote:
> >
> > potentially a dumb question, but do the settings in
> > files/fs-perms.txt affect the building of the base-files rpm just
> > as they would affect the building of a
* Remove duplicate entry for /srv already defined earlier in file.
* Use "${localstatedir}" rather than "/var" for consistency.
Signed-off-by: Robert P. J. Day <rpj...@crashcourse.ca>
---
i'm assuming neither of these changes would cause any trouble.
diff --git a
, but the running image it was being
installed into had a regular /var/log directory, and that caused the
package installation to fail. am i correct in assuming that is normal
behaviour?
thank you kindly.
rday
--
Robert P. J. Day
estions while i'm there.
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http
://github.com/gavincarr/mod_auth_tkt.git
then it works fine. but i'm sure i previously didn't need to do
that. has the behaviour of devtool changed in that respect?
rday
--
Robert P. J. Day
On Mon, 6 Mar 2017, Mark Hatle wrote:
> FYI, I'm experiencing the same issue on master.
>
> --Mark
>
> On 2/20/17 11:40 AM, Burton, Ross wrote:
> >
> > On 20 February 2017 at 11:54, Robert P. J. Day <rpj...@crashcourse.ca
> > <mailto:rpj...@crashcourse.ca>
On Fri, 3 Mar 2017, Jack Mitchell wrote:
> On 03/03/17 10:06, Robert P. J. Day wrote:
> > On Fri, 3 Mar 2017, Anders Darander wrote:
> >
> >> * Robert P. J. Day <rpj...@crashcourse.ca> [170302 12:33]:
> >>
> >>> On Thu, 2 Mar 2017, Robert P.
On Fri, 3 Mar 2017, Anders Darander wrote:
> * Robert P. J. Day <rpj...@crashcourse.ca> [170302 12:33]:
>
> > On Thu, 2 Mar 2017, Robert P. J. Day wrote:
>
> > > inherit pypi setuptools
> > > require python-psutil.inc
>
> > > and the corres
already exists.
^ SSTATE_MIRRORS?
rday
--
============
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcou
On Thu, 2 Mar 2017, Robert P. J. Day wrote:
> possibly a "best practices" question ... regarding recipe for
> "python-psutil" (although this applies for numerous python recipes),
> wind river linux 8 has a recipe for python-psutil_2.2.1.bb which
> in
cipes to
appreciate if this distinction is necessary or not. can someone
clarify this? thanks.
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter:
201 - 300 of 1037 matches
Mail list logo
