summaryrefslogtreecommitdiff
path: root/config/grub/default/patches/0001-borderfix
diff options
context:
space:
mode:
authorLeah Rowe <leah@libreboot.org>2025-01-04 19:24:53 +0000
committerLeah Rowe <leah@libreboot.org>2025-01-04 19:24:53 +0000
commitfc4ee88e167c8a8a537a57e7d44f643ffff19385 (patch)
tree5648e6df5fae45bfb22ba126c62329d1f5d8cd3b /config/grub/default/patches/0001-borderfix
parent8819a93d89bbb2aa7136b22d1b71a04a2dc28cc8 (diff)
vendor.sh: error out if nuking failed
We already have code to handle this, but it's possible that I might break it in the future, due to the complex logic of this script. So, I've implemented this catch-all check at the end of the process. It still relies on the actual setting of the variables, upon which this check is based, to be set correctly. This condition will most certainly never be met, unless I break some other part of the code in the future. That is precisely what this overly pedantic check is for. Example scenarios: I forget to set xchanged=y, on a new modification. I set has_hashes erroneously. The variables are re-used between runs, and not properly reset; at present, a given run of ./mk inject only operates on a single target, but this latter fact could change in the future. need_files is set erroneously; vendorfiles detected as being required, when they aren't. These are just a few examples. As such, this is a preventative bug fix, because it's preventing a bug. The main reason I want this i n here is because I need to ensure that vendor files are properly deleted, for a given release. If I accidentally includes ones that I'm not supposed to, inside ROM images, that could be a big problem. Signed-off-by: Leah Rowe <leah@libreboot.org>
Diffstat (limited to 'config/grub/default/patches/0001-borderfix')
0 files changed, 0 insertions, 0 deletions