From: Matt Hoosier <matt.hoosier@...> Insert an explicit pass to fetch all blobs needed by Git LFS, during the fetch() function. This avoids the default behavior of Git LFS to wait until 'git

From: Mauro Queirós <maurofrqueiros@...> Function "contains_lfs" was only looking at the master branch when searching for LFS content. LFS may be configured in specific branches only, so we

There is a patch in bitbake master related to this which you may want to test and maybe request for adding to dunfell if it

Signed-off-by: Richard Purdie <richard.purdie@...> --- README | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README b/README index c17f74a..af3ace9 100644 --- a/README +++

Signed-off-by: Richard Purdie <richard.purdie@...> --- .../libiconv/libiconv/autoconf270.patch | 17 +++++++++++++++++ recipes-support/libiconv/libiconv_1.15.bb | 3

Signed-off-by: Richard Purdie <richard.purdie@...> --- .../grep/grep-2.5.1a/autoconf270.patch | 27 +++++++++++++++++++ recipes-extended/grep/grep_2.5.1a.bb | 1 + 2

Signed-off-by: Richard Purdie <richard.purdie@...> --- .../diffutils/diffutils-2.8.1/autoconf270.patch | 17 +++++++++++++++++ recipes-extended/diffutils/diffutils_2.8.1.bb | 1 +

Signed-off-by: Richard Purdie <richard.purdie@...> --- .../bash/bash-3.2.57/autoconf270.patch | 17 +++++++++++++++++ recipes-extended/bash/bash_3.2.57.bb | 1 +

I managed to get a workaround by using a do_rootfs postfunc, here it is in case anyone else finds it useful do_rootfs[depends] += "virtual/kernel:do_deploy" do_rootfs[postfuncs] +=

lists.yoctoproject.org wrote: How are you running it? You've said you want it to run after do_install but not what should trigger it. Adding "before do_build" to the addtask line for example might

Hello I created a new task that I want to run for every recipe of my image but only for target recipes and skip all native, sdk,... mytask.bbclass: addtask do_mytask after do_install do_mytask() {

Hi, I have repo where I'm using lfs. I've added to my SRC_URI = "git://...... ;lfs=1" and the project is fetched but the issue is that lfs files are shown as references only (content is not

LOCALEDIR should be set to target path, e.g. /usr/share/locale not host absolute path. This prevent to build reproducible package. LOCALEDIR constructed from: $(DESTDIR)$(PREFIX)/share/locale Change

interesting idea, i hadn't considered that. in the meantime, i think we'll ponder what the structure of the new layer will look like, and put together a first pass. rday

We would also find an official layer for gems interesting. We are currently using the old ruby.bbclass from the meta-ruby layer from openemebedded to build the gems. We are also particularly

BBEXTEND = “native” is a perfectly fine patch to submit to meta-python. We tend to only make those changes when needed (as in your use case) rather than universally. Please submit a patch :)

lists.yoctoproject.org wrote: You could add a "do_deploy" task that places it there. See meta/classes/deploy.bbclass and other recipes which add such a task. Cheers, Richard

OK, Making some progress. I added a package_tar to my conf file and now I get a nice little tar file with my app and its helpers in it! I might also play with the do_deploy command and see

Regardless of its home, there seems to be interest in such a layer. There is nothing stopping you from registering in the layer in the layer index and see where it goes from there. Ruby was part of

Thanks Khem and Chuck! Yes, the application is built in its own bitbake recipe. I do see that there are rpm files built for the application, and that may be a way to upgrade