tree ded624540c8bb0e0f752f315a1cbfcbe6537a5ef
parent 7ea0cb3a94ab9cd5278245bb023d6861d22381e1
author lambdadroid <lambdadroid@gmail.com> 1636797995 +0100
committer LuK1337 <priv.luk@gmail.com> 1729289762 +0200
gpgsig -----BEGIN SSH SIGNATURE-----
 U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgGthemkU6gim2KOhW5Ar1LS2mX2
 caEY7FbNlmpHNtPOIAAAADZ2l0AAAAAAAAAAZzaGE1MTIAAABTAAAAC3NzaC1lZDI1NTE5
 AAAAQKskPy+2DD7I/8/sQDP1GDj7b6cIXgnNLsY94R+FxYtl1ozhI0loi/2vTwNar9ikie
 1w7DCyTbg57UybysVMAgo=
 -----END SSH SIGNATURE-----

build: Respect fs_config when generating recovery ramdisk

Without the -d $(TARGET_OUT) option for mkbootfs, only the
compiled-in fs_config (from AOSP) is used for the generated
ramdisk image. Device-specific additions are ignored.

This is why AOSP sets this option for both the boot- and recovery
ramdisk [1]. However, the option was removed for the recovery ramdisk
in review.lineageos.org/c/LineageOS/android_build/+/222722

This causes device-specific fs_config additions to be ignored when
generating the recovery ramdisk, potentially setting the wrong
permissions.

[1]: android.googlesource.com/platform/build/+/refs/tags/android-9.0.0_r37/core/Makefile#1388

Change-Id: I0f77a49d8b2f08791e60b34ddbb6f3b32bc2f0bc