chore(config/common): remove dead FAST_CREATE_IMAGE variable#9756
Conversation
Declared in config/sources/common.conf since 2022-11 (RISC-V import, commit 3e701a8) but never read anywhere in the build. Removing the zombie declaration to avoid suggesting the framework has a 'fast image creation' switch that users could enable. Confirmed dead by repo-wide grep (only the declaration itself matches) and by GitHub code-search across armbian/build. Signed-off-by: Igor Velkov <325961+iav@users.noreply.github.com>
📝 WalkthroughWalkthroughA single global default configuration variable ( ChangesConfiguration Variable Removal
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
✅ This PR has been reviewed and approved — all set for merge! |
Summary
declare -g FAST_CREATE_IMAGE='yes'fromconfig/sources/common.conf. The variable has zero readers in the current tree.Why this is dead
FAST_CREATE_IMAGEwas a real switch once — selecting betweendd(slow, safe) andtruncate(fast, sparse) for the blank rootfs image. Its life:3ddd91de7(#2365)lib/functions/image/partitioning.sh(if [[ $FAST_CREATE_IMAGE == yes ]]; then truncate ... else dd ...).7b6d9f162(#3639)"yes"by addingFAST_CREATE_IMAGE="yes"to the per-arch configs (amd64.conf,armhf.conf, ...).72cf555bc(armbian-next)partitioning.shswitched to unconditionaltruncate. Commit subject:bye bye $FAST_CREATE_IMAGE: always use truncate for blank image.3e701a857(#4387, initial RISC-V)export FAST_CREATE_IMAGE='yes'was planted in the newconfig/sources/common.conf. By this point the consumer had been gone for ~6 weeks.62f5fe159export ...→declare -g .... No semantic change.So the line in
common.confis a leftover from a 2022 merge that re-introduced the variable into the new common-config location ~6 weeks after the only code path that read it had been deleted. It has been a no-op ever since.Why remove it
*=yesflag with no consumers reads as documentation that the framework supports a "fast image creation" mode users can toggle. It does not —truncateis unconditional.FAST_CREATE_IMAGE=no(the previously meaningful override) silently does nothing today.config-dump-json/diagnostics output, padding the surface area of "knobs the build supports".Test plan
bash lib/tools/shellcheck.sh config/sources/common.confpasses (Congrats, no error's detected in config/sources.)git grep -n FAST_CREATE_IMAGEreturns nothingarmbian/buildper GitHub code-search🤖 Assisted-by: Claude: claude-opus-4-7