Skip to content
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

Open
1 task done
matthijskooijman opened this issue Mar 8, 2024 · 6 comments
Open
1 task done

config-default.conf no longer read by default? #6374

matthijskooijman opened this issue Mar 8, 2024 · 6 comments

Comments

@matthijskooijman
Copy link
Collaborator

matthijskooijman commented Mar 8, 2024

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:

After the first run of compile.sh a new configuration file config-example.conf and symlink config-default.conf will be created. You may edit it to your needs or create different configuration files using it as a template.

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 load config-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=code

How to reproduce?

./compile.sh

Branch

main (main development branch)

On which host OS are you observing this problem?

Other

Relevant log URL

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Copy link

github-actions bot commented Mar 8, 2024

Jira ticket: AR-2099

@rpardini
Copy link
Member

rpardini commented Mar 8, 2024

@rpardini rpardini closed this as completed Mar 8, 2024
@rpardini
Copy link
Member

rpardini commented Mar 8, 2024

Sorry didn't mean to close

@rpardini rpardini reopened this Mar 8, 2024
@igorpecovnik
Copy link
Member

Yes, I've wrote some bad docs that never got merged

They were few hours ago :) Following "better this half done then totally outdated" principle.

@matthijskooijman
Copy link
Collaborator Author

Thanks for clarifying.

I would suggest also updating this section, since I also suspect that the config-default.conf symlink is no longer created again, and also that section does not document that you can (should, by now) actually pass a config name to the compile.sh script.

@rpardini
Copy link
Member

rpardini commented Mar 9, 2024

Yes, we've to review the rest of the docs, indeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants