i did write that a while back while i was still figuring it out. :-) i agree that it would be inappropriate in the *regular* sections of the docs, but i'm convinced it would be worth explaining in som

it appears (after a *very* cursory investigation) that shared-mime-info-native is included, which drags in xmlto-native, which then drags in docbook stuff. i'll confirm that later. rday

most likely, but as i'm explicitly not installing any documentation, i'm now poking around to see what insists on building that for no apparent reason. rday

years ago, i asked about how to support a small set of closely-related targets using MACHINEOVERRIDES to define how to apply patches in a (somewhat) hierarchical fashion: https://www.yoctoproject.org/

testing building qemuarm64 core-image-minimal from scratch, and noticed it fetching for docbook-xml and docbook-xsl stuff ... is there something that still needs docbook support? i'm about to take a q

... snip ... you can't legitimately expect support for YP 2.0, which is six years old and has been EOLed for quite some time. rday

in current OE, there is no "GPL-2.0" license file, there is "GPL-2.0-only" and "GPL-2.0-or-later" and a bunch of others, so i think you need to pick one of those. rday

On Wed, 10 Mar 2021, Quentin Schulz wrote: ... snip ... > https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-kernel/linux/linux-yocto_5.10.bb#n12 > for example. > > This is an example o

can you point at an actual example of that? i took a look and all the yocto kernel recipes i see use the first form. am i just looking in the wrong place? rday

inspired by my earlier plaintive mewling of "gosh, i wish YP had better ruby support," konrad weihmann put in a ridiculous amount of work and came up with: https://github.com/priv-kweihmann/meta-rubyg

i suspect i know the answer, just want to confirm ... friend tells me yesterday he's working with LTS20, i said, "uh, that's not even out yet," he assures he his company has an early release, but he c

i remember testing this a few years back, and making sure i appreciated the subtleties. i might take a shot at rewriting that section, since i think it has potential for confusion. mostly, warning the

bitbake manual, chapter 3, examples of conditional syntax: https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html#examples correctly distinguishes between A_foo_ap

colleague wants a recipe for libbpf: https://github.com/libbpf/libbpf would anyone have done that already and is willing to let me steal it? rday

here's hoping someone has gone through this and can summarize what i need to do; i'll try to keep it short. migrating all sorts of stuff from (effectively) morty project to (effectively) zeus, and cur

while the "standard" way to disable a systemd service from auto-booting is SYSTEMD_AUTO_ENABLE, i just ran across a number of examples in an existing project that do this: SYSTEMD_SERVICE_${PN} = "" o

(i asked about this on the OE list a couple days ago, but i have more info and wanted to get a bit wider coverage as i really, really want to de-mystify this issue.) on current project, upgrading from

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

i personally am not, so i suspect github is the option. rday

regarding the proposed "meta-rubygems" layer --- which sounds like it's going to take off as it can be initialized quite a lot just from konrad's existing meta-sca layer, what are the options for "off