The-going

@Tonymac32 From the point of view of the build system, this folder looks very detached, like a dark forest, since it is not tracked by git. None of us will...

> @The-going [bb1bb91](https://github.com/armbian/build/commit/bb1bb91f1b334408ae48f05f31b5fad17738a6c9) make more sense? Therefore, for me, this file has lost its actual meaning. All this falls entirely on the shoulders and brain convolutions of the user. Great...

I would prefer if "userpatches" remains and only the user's patches will be in this folder. And in the new folder "userconfig", what Igor suggested, the user configuration will lie....

I add or change the configuration, assuming that the file is exported to main.sh. This is the finish line and nothing should change further. But the export takes place earlier...

It's hard for me in IRC. Automatic translation often changes the meaning of what is said to the opposite. I have to make a double transfer to control this.

> lib/configuration.sh:539: source "${CONFIG_PATH}"/lib.config This can be left as it is. > lib/main.sh:130: source "${CONFIG_PATH}"/lib.config Here we need to change the name, for example, lib.reconfigure

> We should be asking.... > > Why do we need to reconfigure? > Does this code block just need to be refactored? If at this point it is necessary...

I will continue in other words. If you want to reorganize the "userpatches" folder, please, please leave this name and the entire structure of the user's patches unchanged. The best...

> I am against adding another untracked folder for the sake of organization in the /build directory There are already many of [these folders](https://github.com/armbian/build/blob/fcb8b6f195bbb76c83c612c425fdf08cfd48c68b/.gitignore#L18). And there's nothing we can do...

> * further refactor userpatches reference..... `config_path`, `userpatches_path` to more accurate naming We are talking about global variables, which means capital letters and an underscore. I don't understand why, but...