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

Conflicting dependencies yields inconsistent dependency graph #236

Open
ccollins476ad opened this issue Nov 7, 2018 · 0 comments
Open

Comments

@ccollins476ad
Copy link
Contributor

syscfg.vals:
    FOO: 1

syscfg.vals.BAR:
    FOO: 1

These two syscfg.vals mappings are in conflict. The first enables FOO unconditionally; the second only enables FOO if bar is set. When newt encounters a conflict like this, it accepts the first override it sees and discards the others. Since these overrides are not processed in a consistent order, the result varies from build to build.

Newt should not allow such conflicting overrides. Initially, we can make newt emit a warning when it encounters this. Later, we can change it to an error.

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

No branches or pull requests

1 participant