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.
Bundler's built-in rake tasks add pkg/* to rake's CLOBBER list
(so
rake clobber
removes them).That's great for .gem that are created via
rake build
because bundler's rake task writes the .gem to pkg/.However, by default if you run
gem build
instead ofrake build
, you'll end up with the .gem written in the root (next to where the .gemspec is).This adds *.gem to rake's
CLOBBER
list so thatrake clobber
will properly clean any built gems regardless if they were built viarake
orgem
.(It also moves the default task to the top of the file rather than the bottom.
That's the conventional location inherited from
make
whose default task is automatically the first listed target.)