# Raspberry Pi 4 Model B - Yocto 5.0 "scarthgap" and later **URL:** \ **Category:** Yocto Project\ **Tags:** yocto, raspberry-pi-4, scarthgap\ **Created:** [July 17, 2024, 11:05am UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-5-0-scarthgap-and-later/7024 "2024-07-17T11:05:52Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [February 11, 2025, 12:57pm UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-5-0-scarthgap-and-later/7024/5 "2025-02-11T12:57:14Z")
HI @wlbdv, Thanks a lot for reaching out, and nice to hear you found this helpful. For your questions: 1. The core concept of `kas` is that the whole build is defined by the data given, and hence it re-creates `local.conf` based on the passed `.yml` files every time. The way to augment the information in `meta-mender-community` with your local settings is to use an override file as described at [Using kas to reproduce your Yocto builds](https://hub.mender.io/t/using-kas-to-reproduce-your-yocto-builds/6020#local-override-files-4). You would put your additions into a file like `wlbdev-mender.yml`, and then invoke `kas` like `kas shell ../kas/raspberrypi4.yml:wlbdev-mender.yml`. This way, whatever assignments you have in `wlbdev-mender.yml` will overwrite the given defaults. 2. good catch, that’s a leftover from the original `repo`-based tutorial. Fixed now. 3. the `core-image-base-raspberrypi4.mender` file is in fact a symlink to the last built artifact. I have just given it a test build, and after the second build the link is pointing to the newly created `.mender` file. Can you check if this is the case for you? Greetz, Josef --- _[View the full topic](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-5-0-scarthgap-and-later/7024)._