**** BEGIN LOGGING AT Sun Jan 17 02:59:57 2021 Jan 17 17:32:50 Hello everyone. Is there a canonical way to install/add wireguard? I.e. one that uses a kernel module when available and falls back to wireguard-linux-compat otherwise? Jan 17 17:35:30 Actually, i just realised that in both cases there would be a kernel module. It is just that in one case the module is from the main kernel and otherwise its from compat. Jan 17 17:58:27 bantu: maybe https://layers.openembedded.org/layerindex/branch/master/recipes/?q=wireguard helps? Jan 17 19:24:07 neverpanic: I was aware of that, but looking into the .bb files was indeed useful. Thanks Jan 17 19:24:35 Using IMAGE_INSTALL_append = " wireguard-module" I get the problem "package kernel-module-wireguard-1.0.20200401-r0.qemux86_64 requires kernel-module-wireguard-5.4.61-yocto-standard, but none of the providers can be installed" Jan 17 19:35:35 Has anyone got an idea where the MIT in COPYING.MIT comes from? Jan 17 19:55:40 manuel1985: MIT is the name of a license Jan 17 19:57:39 bantu: I see, thanks Jan 17 20:43:42 Hi guys Jan 17 20:43:49 I have a basic issue Jan 17 20:44:39 Am I right that the do_install procedure does not run for an image recipe? Jan 17 20:45:26 If so, how should I deploy some config files from the image recipe? Jan 17 21:07:42 linums: implement a recipe which installs config files in the right places ? Jan 17 21:07:50 linums: what kind of config files exactly ? Jan 17 21:09:00 I've changed the methods os the PAM Jan 17 21:09:24 And those configs I would like to deploy in image generation time Jan 17 21:09:32 Not afterwards Jan 17 21:09:45 So I can not do it from the image recipe? Jan 17 21:10:51 linums: can't you bbappend the libpam_%.bb ? Jan 17 21:11:19 you can , look at IMAGE_POSTPROCESS_COMMAND, but ew Jan 17 21:12:22 Ah, so it should be more like a package installation level job, rather than the image creation job then Jan 17 21:14:01 linums: if it is anything that goes into /etc/pam.d , git grep for 'pam.d', there are many examples Jan 17 21:14:29 I was thinking about the package recipe more like as just purely the package, what I create, and every custom modification as the image level task Jan 17 21:14:40 and yes, either it should be libpam bbappend or some custom libpam-customconfig_...bb which is board-specific and installs the files Jan 17 21:15:05 This sounds reasonable, thanks Jan 17 21:15:32 linums: probably even the later (libpam-customconfig_%.bb), since you dont want to generate board-specific libpam Jan 17 21:15:58 Yeah, right Jan 17 21:16:53 Something, with it's name stating, that it's a config task Jan 17 21:54:14 And what license should I add for a config layer? Jan 17 21:58:07 I see, "closed" Jan 17 22:01:51 paulbarker, paulbarker_tmp: Your Highly Scalable Yocto Project® Build Automation talk is tremendously helpful! Jan 17 22:02:11 linums: What license if your config under? Could also be MIT or similar, depends on your layer Jan 17 22:02:26 https://wiki.yoctoproject.org/wiki/images/archive/0/02/20200702140427%21DD1_Highly_Scalable_Build_Automation_NA20.pdf Jan 17 22:11:22 I meant the config recipe, but this is just a configurator recipe, so I have no license for it Jan 17 22:11:33 linums: then MIT Jan 17 22:11:58 linums: it's just that you should understand what the license means Jan 17 22:12:39 since its just a config file, a non-restrictive license is a good idea Jan 17 22:25:47 See Jan 17 22:26:10 And what should the closed license setup represent? Jan 17 22:31:09 linums: closed means something propriety which you can't share Jan 17 23:05:53 Then, a mit lic is better, right Jan 17 23:54:07 Why am I prevented to add a symlink to a non dev/dbg/nativesdk package? Jan 18 00:04:27 linums: prevented how ? pastebin the error message Jan 18 00:05:10 linums: git grep ln..s in oe-core has plenty of examples Jan 18 00:07:31 marex: maybe it's specific to oath? They use the /usr/lib path, but I created a symlink under /lib to the proper so, so this became the end of it: Jan 18 00:07:33 ERROR: oath-2.6.2-r0 do_package_qa: QA Issue: non -dev/-dbg/nativesdk- package contains symlink .so: oath path '/work/core2-64-poky-linux/oath/2.6.2-r0/packages-split/oath/lib/security/pam_oath.so' [dev-so] **** ENDING LOGGING AT Mon Jan 18 02:59:57 2021