Layered configuration framework #252

New Issue

Jef Roosens · 2022-06-16T23:25:24+02:00

Jef Roosens commented

2022-06-16 23:25:24 +02:00

Lots of configuration variables are useful both on a target level, an arch-repo or a repo level.

For example, a specific target might need some env var to be set. However, another scenario might require the CC variable to be set for every repo (for example, a reopsitory that biulds all its packages using clang). Another scenario (which I already use) is configuring a repository to optimize builds for a given microarchitecture. This would require appending to the CFLAGS variable for every build.

To prevent a mountain of technical debt, I want to design a general system for managing this layered configuration system.

Lots of configuration variables are useful both on a target level, an arch-repo or a repo level. For example, a specific target might need some env var to be set. However, another scenario might require the `CC` variable to be set for every repo (for example, a reopsitory that biulds all its packages using clang). Another scenario (which I already use) is configuring a repository to optimize builds for a given microarchitecture. This would require appending to the `CFLAGS` variable for every build. To prevent a mountain of technical debt, I want to design a general system for managing this layered configuration system.

Jef Roosens added the

idea

label 2022-06-16 23:25:24 +02:00

Jef Roosens added this to the 0.6.0 milestone 2022-06-17 09:32:38 +02:00

Jef Roosens removed this from the 0.6.0 milestone 2022-08-12 17:42:50 +02:00

Sign in to join this conversation.