-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
config-default.conf no longer read by default? #6374
Comments
Jira ticket: AR-2099 |
Yes, I've wrote some bad docs that never got merged, armbian/documentation@ef5befb?short_path=83d55c9#diff-83d55c94e1aeaa5c79c556aab6744acc2e218e79de654b376b561189fb715315 |
Sorry didn't mean to close |
They were few hours ago :) Following "better this half done then totally outdated" principle. |
Thanks for clarifying. I would suggest also updating this section, since I also suspect that the |
Yes, we've to review the rest of the docs, indeed. |
What happened?
I recently upgraded my build repo from an old version, and it seems it no longer reads
userpatches/config-default.conf
by default when I run./compile.sh
. When I explicitly specify it with./compile.sh default
it does get read.Maybe this is intentional and the idea is to now always specify a config name, but the docs seem to suggest (though a bit vaguely) that
config-default.conf
should be loaded by default:Looking at the code, it seems the config filename(s) are stored in
$ARMBIAN_CONFIG_FILES
, but that has no default value and values only get added from commandline arguments, so it seems the code is not even trying to loadconfig-default.conf
by default (which might make this is a documentation bug). See https://github.com/search?q=repo%3Aarmbian%2Fbuild+ARMBIAN_CONFIG_FILES&type=codeHow to reproduce?
Branch
main (main development branch)
On which host OS are you observing this problem?
Other
Relevant log URL
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: