-
Notifications
You must be signed in to change notification settings - Fork 117
[bugfix] Treat conflicts in module mappings properly #1611
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
[bugfix] Treat conflicts in module mappings properly #1611
Conversation
79d3956 to
576ba91
Compare
- The scenario is invalid for this modules system.
teojgo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe also change the documentation for emit_load_commands and emit_unload_commands
You mean the fact that they do not take into account anymore the module mapping? |
No, I mean you should use plural here since you get a list of commands: |
teojgo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm
When modules are mapped with the
-Moption and there are conflicts in the replacement sequence of modules, emit the the module load and unload commands in the correct order.Fixes #1274.