Add weak dependency feature for mrbgems #4129
Closed
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.
This feature is a hint to change the mrbgem inclusion order when specified by
spec.add_dependency
ofmrbgem.rake
.It does not mean that it is depends directly, so it will not include mrbgem by itself.
To use this feature, give the
weak: true
argument to theMRuby::Gem::Specification#add_dependency
method inmruby-XXX/mrbgem.rake
.Example with
mruby-print
andmruby-sprintf
:my_build_config.rb
Build summary of
MRUBY_CONFIG=my_build_config.rb ./minirake clean all
Compatible problems for users
It is not backwards compatible. Also it will always be treated as dependent for previous mruby versions.
Therefore, it is necessary to decide by
require "mruby/source"
andMRuby::Source::MRUBY_RELEASE_NO
.e.g.: