Date   

Re: PREFERRED_VERSION_pn-: which version is selected?

Mauro Ziliani
 

My purpose is this.

For image-recipe_1.0.0 I need recip1 version 0.9

For image-recipe_1.1.0 I need recip1 version 1.0


How I can solve this?


Best regards

  MZ

Il 08/02/21 12:09, Josef Holzmayr ha scritto:
Howdy!

Am Mo., 8. Feb. 2021 um 11:52 Uhr schrieb Mauro Ziliani <mauro@faresoftware.it>:
In the image recipe I put

image-recipe.bb

IMAGE_INSTALL_append := " \
recipe1 \
"

PREFERRED_VERSION_pn-recipe1 := "0.9"
As usual, recipe data is local, conf data is global. Setting things
that should affect other recipes (like PREFERRED_VERSION) does not
work inside a recipe - and an image recipe is still just a recipe.
This needs to go into the DISTRO config, usually.

Greetz


Re: PREFERRED_VERSION_pn-: which version is selected?

Quentin Schulz
 

Hi Mauro,

On Mon, Feb 08, 2021 at 11:52:33AM +0100, Mauro Ziliani wrote:
Hi all.

I'm working with Krogoth on imx6


I have the same recipe with different versions

recipe1_0.9.bb

recipe1_1.0.bb


In the image recipe I put


image-recipe.bb

IMAGE_INSTALL_append := " \

    recipe1 \

"

PREFERRED_VERSION_pn-recipe1 := "0.9"
Yocto chant #1: Recipe data is local, conf data is global.

In other words, you cannot modify other recipes from one recipe.

Since image recipes are recipes, your PREFERRED_VERSION ni your image
recipe is effectively a no-op.

On a side note, := operator is rarely seen outside of
FILESEXTRAPATHS_prepend in bbappend, try to keep it this way.


If I do

 bitbake -s

I get

recipe1    :1.0-r0


If I do

bitbake image-recipe


in image-recipe.manifest I look

recipe1  1.0-r0


Why is not selected the preferred version?

How can I choose the recipe's version I'd like?
In a configuration file: local.conf, distro.conf, machine.conf.

Though, it is heavily discouraged to use local.conf for anything except
debugging sessions, as it is meant only for **local** configuration and
isn't supposed to be versioned.

Cheers,
Quentin


Re: PREFERRED_VERSION_pn-: which version is selected?

Martin Jansa
 

And the variable should be named PREFERRED_VERSION_recipe1 (it's not using pn as an override).


On Mon, Feb 8, 2021 at 12:10 PM Josef Holzmayr <jester@...> wrote:
Howdy!

Am Mo., 8. Feb. 2021 um 11:52 Uhr schrieb Mauro Ziliani <mauro@...>:
> In the image recipe I put
>
> image-recipe.bb
>
> IMAGE_INSTALL_append := " \
>      recipe1 \
> "
>
> PREFERRED_VERSION_pn-recipe1 := "0.9"

As usual, recipe data is local, conf data is global. Setting things
that should affect other recipes (like PREFERRED_VERSION) does not
work inside a recipe - and an image recipe is still just a recipe.
This needs to go into the DISTRO config, usually.

Greetz




Re: PREFERRED_VERSION_pn-: which version is selected?

Josef Holzmayr
 

Howdy!

Am Mo., 8. Feb. 2021 um 11:52 Uhr schrieb Mauro Ziliani <mauro@faresoftware.it>:
In the image recipe I put

image-recipe.bb

IMAGE_INSTALL_append := " \
recipe1 \
"

PREFERRED_VERSION_pn-recipe1 := "0.9"
As usual, recipe data is local, conf data is global. Setting things
that should affect other recipes (like PREFERRED_VERSION) does not
work inside a recipe - and an image recipe is still just a recipe.
This needs to go into the DISTRO config, usually.

Greetz


PREFERRED_VERSION_pn-: which version is selected?

Mauro Ziliani
 

Hi all.

I'm working with Krogoth on imx6


I have the same recipe with different versions

recipe1_0.9.bb

recipe1_1.0.bb


In the image recipe I put


image-recipe.bb

IMAGE_INSTALL_append := " \

    recipe1 \

"

PREFERRED_VERSION_pn-recipe1 := "0.9"


If I do

 bitbake -s

I get

recipe1    :1.0-r0


If I do

bitbake image-recipe


in image-recipe.manifest I look

recipe1  1.0-r0


Why is not selected the preferred version?

How can I choose the recipe's version I'd like?


Best regards,

   MZ


Re: devtool question/issue

Josef Holzmayr
 

Hi David!

Am Mo., 8. Feb. 2021 um 01:01 Uhr schrieb David Gartner <gartnerd@gmail.com>:
I found the issue that was causing my problem. Just an FYI if anyone else happens to run into this.

There was a file named ".devtoolbase" in /mnt/YB. I think this was a remenant of some previous work I was doing with yocto. I'm not sure what the purpose of this file is but once I removed it devtool no longer errorred out.
Oh great, thanks for the heads up. I am actually the one who did the
video, and just returned into office mondayishly and would have tried
probably this afternoon. But that I would have never found, as I
usually start out in clean slate containers, and I use devtool a lot
in there with builds even scattered out over multiple mount points.So
glad you figurede out and took the time to share!

Greetz


Re: #yocto CORE_IMAGE_EXTRA_INSTALL Where can I find a list of valid package names? #yocto

Mike Looijmans
 

Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands

T: +31 (0) 499 33 69 69
E: mike.looijmans@topicproducts.com
W: www.topicproducts.com

Please consider the environment before printing this e-mail
On 04-02-2021 09:12, Josef Holzmayr via lists.yoctoproject.org wrote:
oe-pkgdata-util list-pkgs
Oh, I've been using OE from the times I still had hair on my head, but never found this gem. Thanks for the tip!

--
Mike Looijmans


[meta-selinux][PATCH] remove obsolete e2fsprogs bbappend

hongxu
 

Since oe-core commit [f51835e022 e2fsprogs: upgrade 1.45.6 -> 1.45.7] applied,
the backport misc_create_inode.c-label_rootfs.patch is not required

The lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch is not used by the recipe,
so also remove it.

Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
---
.../e2fsprogs/e2fsprogs_%.bbappend | 1 -
.../e2fsprogs/e2fsprogs_selinux.inc | 3 --
...t2fs-ext2_ext_attr.h-add-xattr-index.patch | 20 ---------
.../misc_create_inode.c-label_rootfs.patch | 45 -------------------
4 files changed, 69 deletions(-)
delete mode 100644 recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
delete mode 100644 recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
delete mode 100644 recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
delete mode 100644 recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch

diff --git a/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend b/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
deleted file mode 100644
index 7719d3b..0000000
--- a/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
+++ /dev/null
@@ -1 +0,0 @@
-require ${@bb.utils.contains('DISTRO_FEATURES', 'selinux', '${BPN}_selinux.inc', '', d)}
diff --git a/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc b/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
deleted file mode 100644
index 9cbb7fe..0000000
--- a/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
+++ /dev/null
@@ -1,3 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
-
-SRC_URI += "file://misc_create_inode.c-label_rootfs.patch"
diff --git a/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch b/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
deleted file mode 100644
index b87c414..0000000
--- a/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
+++ /dev/null
@@ -1,20 +0,0 @@
-Add xattr name index for xattrs with the 'security' prefix. These are defined
-in the ext(2|3|4)/xattr.h in the kernel. We use the EXT2 prefix for consistency
-with e2fslibs naming.
-
-Signed-off-by: Philip Tricca <flihp@twobit.us>
-
-Index: e2fsprogs-1.42.9/lib/ext2fs/ext2_ext_attr.h
-===================================================================
---- e2fsprogs-1.42.9.orig/lib/ext2fs/ext2_ext_attr.h
-+++ e2fsprogs-1.42.9/lib/ext2fs/ext2_ext_attr.h
-@@ -15,6 +15,9 @@
- /* Maximum number of references to one attribute block */
- #define EXT2_EXT_ATTR_REFCOUNT_MAX 1024
-
-+/* Name indexes */
-+#define EXT2_XATTR_INDEX_SECURITY 6
-+
- struct ext2_ext_attr_header {
- __u32 h_magic; /* magic number for identification */
- __u32 h_refcount; /* reference count */
diff --git a/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch b/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch
deleted file mode 100644
index 046e521..0000000
--- a/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch
+++ /dev/null
@@ -1,45 +0,0 @@
-From: Philip Tricca <flihp@twobit.us>
-To: tytso@mit.edu
-Cc: liezhi.yang@windriver.com
-Date: Sat, 20 Feb 2016 18:58:58 +0000
-Subject: [PATCH] misc/create_inode.c: Copy xattrs from root directory when populating fs.
-
-When copying a file system using the -d option the xattrs from the root
-directory need to be copied before the populate_fs recusion starts.
-
-Signed-off-by: Philip Tricca <flihp@twobit.us>
-Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
-
----
- misc/create_inode.c | 8 ++++++++
- 1 file changed, 8 insertions(+)
-
-diff --git a/misc/create_inode.c b/misc/create_inode.c
-index a7b6d348..cfd15922 100644
---- a/misc/create_inode.c
-+++ b/misc/create_inode.c
-@@ -979,6 +979,13 @@ errcode_t populate_fs2(ext2_filsys fs, ext2_ino_t parent_ino,
- return retval;
- }
-
-+ retval = set_inode_xattr(fs, root, source_dir);
-+ if (retval) {
-+ com_err(__func__, retval,
-+ _("while setting xattrs for \"%s\""), source_dir);
-+ goto out;
-+ }
-+
- file_info.path_len = 0;
- file_info.path_max_len = 255;
- file_info.path = calloc(file_info.path_max_len, 1);
-@@ -987,6 +994,7 @@ errcode_t populate_fs2(ext2_filsys fs, ext2_ino_t parent_ino,
- &file_info, fs_callbacks);
-
- free(file_info.path);
-+out:
- free(hdlinks.hdl);
- return retval;
- }
---
-2.11.1
-
--
2.29.2


Re: devtool question/issue

David Gartner <gartnerd@...>
 

I found the issue that was causing my problem. Just an FYI if anyone else happens to run into this.

There was a file named ".devtoolbase" in /mnt/YB. I think this was a remenant of some previous work I was doing with yocto. I'm not sure what the purpose of this file is but once I removed it devtool no longer errorred out.


[meta-selinux][PATCH] e2fsprogs: remove bbappend

Yi Zhao
 

Remove bbappend since the misc_create_inode.c-label_rootfs.patch has
been merged upstream[1].

[1] https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=7616fd6a599e44c5700c2c3a2e08979c6c5c747e

Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
---
.../e2fsprogs/e2fsprogs_%.bbappend | 1 -
.../e2fsprogs/e2fsprogs_selinux.inc | 3 --
...t2fs-ext2_ext_attr.h-add-xattr-index.patch | 20 ---------
.../misc_create_inode.c-label_rootfs.patch | 45 -------------------
4 files changed, 69 deletions(-)
delete mode 100644 recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
delete mode 100644 recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
delete mode 100644 recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
delete mode 100644 recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch

diff --git a/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend b/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
deleted file mode 100644
index 7719d3b..0000000
--- a/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
+++ /dev/null
@@ -1 +0,0 @@
-require ${@bb.utils.contains('DISTRO_FEATURES', 'selinux', '${BPN}_selinux.inc', '', d)}
diff --git a/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc b/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
deleted file mode 100644
index 9cbb7fe..0000000
--- a/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
+++ /dev/null
@@ -1,3 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
-
-SRC_URI += "file://misc_create_inode.c-label_rootfs.patch"
diff --git a/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch b/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
deleted file mode 100644
index b87c414..0000000
--- a/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
+++ /dev/null
@@ -1,20 +0,0 @@
-Add xattr name index for xattrs with the 'security' prefix. These are defined
-in the ext(2|3|4)/xattr.h in the kernel. We use the EXT2 prefix for consistency
-with e2fslibs naming.
-
-Signed-off-by: Philip Tricca <flihp@twobit.us>
-
-Index: e2fsprogs-1.42.9/lib/ext2fs/ext2_ext_attr.h
-===================================================================
---- e2fsprogs-1.42.9.orig/lib/ext2fs/ext2_ext_attr.h
-+++ e2fsprogs-1.42.9/lib/ext2fs/ext2_ext_attr.h
-@@ -15,6 +15,9 @@
- /* Maximum number of references to one attribute block */
- #define EXT2_EXT_ATTR_REFCOUNT_MAX 1024
-
-+/* Name indexes */
-+#define EXT2_XATTR_INDEX_SECURITY 6
-+
- struct ext2_ext_attr_header {
- __u32 h_magic; /* magic number for identification */
- __u32 h_refcount; /* reference count */
diff --git a/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch b/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch
deleted file mode 100644
index 046e521..0000000
--- a/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch
+++ /dev/null
@@ -1,45 +0,0 @@
-From: Philip Tricca <flihp@twobit.us>
-To: tytso@mit.edu
-Cc: liezhi.yang@windriver.com
-Date: Sat, 20 Feb 2016 18:58:58 +0000
-Subject: [PATCH] misc/create_inode.c: Copy xattrs from root directory when populating fs.
-
-When copying a file system using the -d option the xattrs from the root
-directory need to be copied before the populate_fs recusion starts.
-
-Signed-off-by: Philip Tricca <flihp@twobit.us>
-Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
-
----
- misc/create_inode.c | 8 ++++++++
- 1 file changed, 8 insertions(+)
-
-diff --git a/misc/create_inode.c b/misc/create_inode.c
-index a7b6d348..cfd15922 100644
---- a/misc/create_inode.c
-+++ b/misc/create_inode.c
-@@ -979,6 +979,13 @@ errcode_t populate_fs2(ext2_filsys fs, ext2_ino_t parent_ino,
- return retval;
- }
-
-+ retval = set_inode_xattr(fs, root, source_dir);
-+ if (retval) {
-+ com_err(__func__, retval,
-+ _("while setting xattrs for \"%s\""), source_dir);
-+ goto out;
-+ }
-+
- file_info.path_len = 0;
- file_info.path_max_len = 255;
- file_info.path = calloc(file_info.path_max_len, 1);
-@@ -987,6 +994,7 @@ errcode_t populate_fs2(ext2_filsys fs, ext2_ino_t parent_ino,
- &file_info, fs_callbacks);
-
- free(file_info.path);
-+out:
- free(hdlinks.hdl);
- return retval;
- }
---
-2.11.1
-
--
2.25.1


Re: devtool question/issue

David Gartner <gartnerd@...>
 

After some experimentation it appears that devtool does not like running from a filesystem volume that does not contain my home directory. 

My current setup on a virtualized host has the following volumes:

Filesystem      Size  Used Avail Use% Mounted on

udev             32G     0   32G   0% /dev

tmpfs           6.3G  5.7M  6.3G   1% /run

/dev/sda         25G   11G   13G  46% /

tmpfs            32G     0   32G   0% /dev/shm

tmpfs           5.0M     0  5.0M   0% /run/lock

tmpfs            32G     0   32G   0% /sys/fs/cgroup

/dev/sdc        148G   39G  102G  28% /mnt/YB

tmpfs           6.3G     0  6.3G   0% /run/user/1000

My home directory is located on /dev/sda - devtool works for yocto projects on this volume

/dev/sdc - I added this volume so that I'd have more space while using yocto, but devtool complains and doesn't run here. I deleted the contents of /dev/sdc and re-tried following the tutorial given in my initial post. I can reproduce (e.g. create and run qemuarm images) everything upto the step where devtool needs to be used.

The short term solution would be to increase the size of /dev/sdc but this requires moving up to a more expensive plan from my cloud provider.

Any insight as to why this occurs


Re: [meta-virtualization]: dunfell docker run issues

Leon Woestenberg
 

Marek,

This might indeed indicate a configuration mismatch. Lots of stuff
comes up on Google that you might want to check.

One is a change in systemd that affects this. Sorry I don't have a
link ready anymore.

Regards,

Leon.




--
Leon Woestenberg
leon@sidebranch.com
T: +31 40 711 42 76
M: +31 6 472 30 372

Sidebranch Embedded Systems
Eindhoven, The Netherlands
http://www.sidebranch.com

On Thu, Feb 4, 2021 at 4:04 PM Marek Belisko <marek.belisko@gmail.com> wrote:

Hi,

I'm trying to run docker containers on orangepi and use
meta-virtualization layer to add docker. I've installed the docker-ce
package and everything seems to be fine.

But docker service seems fails to start with:
Feb 04 15:00:01 orange-pi-zero dockerd[495]: failed to start daemon:
Devices cgroup isn't mounted

I was trying to add various options to kernel command line like
described here: https://github.com/docker/cli/issues/2104

but it doesn't work. My command-line looks like:
...systemd.unified_cgroup_hierarchy=0 cgroup_enable=memory
cgroup_memory=1 swapaccount=1 cgroup_no_v1=all

Any other ideas what to check? Thanks a lot.

BR,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com



Re: devtool question/issue

David Gartner <gartnerd@...>
 

Thanks for the suggestion. I gave it a try but I still get the same result/error :( 


Re: devtool question/issue

Gary Huband
 

I always start with

devtool modify <package>

This sets-up the workspace,  puts the package source code in workspace/sources, inits git, etc.

Gary


From: yocto@... <yocto@...> on behalf of David Gartner via lists.yoctoproject.org <gartnerd=gmail.com@...>
Sent: Friday, February 5, 2021 8:06 PM
To: yocto@... <yocto@...>
Subject: [yocto] devtool question/issue
 
Hi,

I've been following along on this youtube video created by a Yocto developer:


I can reproduce everything presented until it comes to using devtool (as shown at the time index in the link given above). When attempting to run:

devtool add git://blah-blah-gitrepo

I get the error:

ERROR: workspace layer not set up


My understanding from the documentation is that the "workspace" layer gets created (if it doesn't exist) when running devtool with a command such as add.

Since I'm new at using Yocto, it's likely that I"m missing something fundamental here. 

Any help/suggestions would be appreciated

Gary Huband
Sr. Software and Systems Engineer

Office: 434.284.8071 x720
Direct: 434.260.4995
Gary@...

Follow Us!
LinkedIn  |  Blog  |  Website

: : : : : : : : : : : : : : : : : : : : : : : : : : :

MSi

This email and any files transmitted with it are confidential and proprietary and intended solely for the use of the individual or entity to whom they are addressed. Any dissemination, distribution or copying of this communication is strictly prohibited without our prior permission. If you received this in error, please contact the sender and delete the material from any computer.


Re: [meta-virtualization]: dunfell docker run issues

Robert Berger
 

Hi,

On 04/02/2021 17:03, Marek Belisko wrote:
Hi,
I'm trying to run docker containers on orangepi and use
meta-virtualization layer to add docker. I've installed the docker-ce
package and everything seems to be fine.
But docker service seems fails to start with:
Feb 04 15:00:01 orange-pi-zero dockerd[495]: failed to start daemon:
Devices cgroup isn't mounted
Can you please tell us which version of yocto this is?

Also which kernel and especially which kernel config.

I use something pretty recent (master kind of) and I am able to start docker and podman with a custom kernel, but networking is very wrong.

e.g.
1) if I run a web service in a container and open port 8080 to the outside world it is not accessible.

2) it's also not possible with docker-compose/podman-compose to communicate between containers

... unless I put everything on the host network.

Once you reconfigure your kernel and get it up and running could you please also test the issues I mention here?

BTW will dunfell it seems to work, I need to retest, but I have some boards running with it, I believe.

If you manage to get an upstream kernel to run on your orangepi zero I guess I could even give you my layers to give it a try. You will need another device tree and boot loader, but the rest should work.

Regards,

Robert


devtool question/issue

gartnerd@...
 

Hi,

I've been following along on this youtube video created by a Yocto developer:


I can reproduce everything presented until it comes to using devtool (as shown at the time index in the link given above). When attempting to run:

devtool add git://blah-blah-gitrepo

I get the error:

ERROR: workspace layer not set up


My understanding from the documentation is that the "workspace" layer gets created (if it doesn't exist) when running devtool with a command such as add.

Since I'm new at using Yocto, it's likely that I"m missing something fundamental here. 

Any help/suggestions would be appreciated


Re: Appropriate patch posting location?

Leon Woestenberg
 

Hi Kent,

On Fri, Feb 5, 2021 at 5:14 PM Kent Dorfman <kent.dorfman766@gmail.com> wrote:

Is there not a separate list address to post patches, so as to keep
discussion and patch lists separate?

It can be an issue for folks who are on web mailers that make you
delete messages one-at-a-time.... ie "traditional frames based gmail
interface"
Most of these providers provide an IMAP interface as well, such as gmail.

Also, in gmail you can tag messages to move into a separate folder for
easy delete.
For devs and users, the patches are useful info as to what gets
changed, I like them to be intermixed.

Regards,


Leon.


Re: #yocto CORE_IMAGE_EXTRA_INSTALL Where can I find a list of valid package names? #yocto

Leon Woestenberg
 

Hello,

On Fri, Feb 5, 2021 at 5:27 PM Yi Fan Yu <yifan.yu@windriver.com> wrote:

new here, pointing out of the obvious? website

https://layers.openembedded.org/
What's obvious? There are no package names there, only recipe names
that I am aware of.

So for the non-obvious packages it still is a bit of guesswork, or the
responses in this thread.

Regards,

Leon.


Re: #yocto CORE_IMAGE_EXTRA_INSTALL Where can I find a list of valid package names? #yocto

Yi Fan Yu
 

new here, pointing out of the obvious? website

https://layers.openembedded.org/


On 2/4/21 4:36 AM, Quentin Schulz wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]

Hi David,

On Thu, Feb 04, 2021 at 01:24:35AM -0700, David Babich wrote:
Thanks for that reply.  I actually deleted my message from the forum post
because I thought maybe I hadn't dug through things enough and perhaps I
was wasting people's time.  But I think you provided some validation to my
question.  I'm more used to the typical ncurses method of configuration of
the old days with a kernel config a rootfs config etc.   I will try your
suggested command.  But I'm wondering are the names typical of what I might
expect if I were to do something like "sudo apt-get install <whatever>"
Not always. E.g. debian packages are renamed if they only have a library
in it to be the name of said library. This does not happen for rpm and
opkg. Note: this is a vague memory, I don't use de packages in Yocto so
to be taken with a grain of salt.

(which is somewhat of an experience thing) or do I just simply need to dig
around on web searches to find out what the actual name is.  I've found
Not web searches. Basically, one would need to identify the recipe
building the software in the package you want to find.
From there, you can read the list of packages in PACKAGES (sometimes,
like for gstreamer plugins for example, it is dynamically set so you
won't be able to find them by just reading the recipe (though you can
more or less guess them)).

To know what's inside one of the packages without baking the recipe, one
would need to have a look at the FILES_${PN}<-xxx> variables.

It's therefore mostly knowledge and trial and errors as Josef said.

The difficulty for the Yocto project to compile a list of packages and
which recipe build them is that packages can depend on configuration
files (machines, distros, ...). Sometimes they do appear, sometimes not.
Sometimes a package for a distro contains more than a package for
another distro while having the same name.

Which is also a reason why ncurses/menuconfig would be hard for Yocto
Project, because content of packages are not guaranteed to be identical
between machines and distros, so it'd be hard to give descriptions of
options to select.

Hope this helps,
Quentin




Appropriate patch posting location?

Kent Dorfman
 

Is there not a separate list address to post patches, so as to keep
discussion and patch lists separate?

It can be an issue for folks who are on web mailers that make you
delete messages one-at-a-time.... ie "traditional frames based gmail
interface"

1581 - 1600 of 53814