Add umpf-flags support to control the EXTRAVERSION patching #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support to specify umpf-flags which influence the umpf build behaviour. The flags are tracked within the umpf tag via the new 'umpf-flags' section. Users can flags directly via the useries or by specfiy them via the command line option '--flags'.
The EXTRAVERSION patch conflicts if a stable update is done without using umpf, e.g. if multiple parties do stable updates for certain software package like Linux but only a few of them use umpf.
To avoid EXTRAVERSION conflicting each time a stable update is done we shift the EXTRAVERSION patching down into the middle of the Makefile by using the new umpf-flags mechanism:
New flags can be added by extending the SUPPORTED_FLAGS list and adding the flag_ array, e.g.:
To use the flag, you need to check the value, e.g.: