diff options
| author | The Bundler Bot <bot@bundler.io> | 2018-04-28 06:37:55 +0000 |
|---|---|---|
| committer | The Bundler Bot <bot@bundler.io> | 2018-04-28 06:37:55 +0000 |
| commit | 0c5d3b8c1f391aa5175321675ecd91ee6a1f231b (patch) | |
| tree | d7e13fc4844d9fbf367ac2ef02c3bab81d7a9dad /man/bundle-lock.ronn | |
| parent | 948771063c05a56af8888acf5c01171293371214 (diff) | |
| parent | 00fd58eaa69015092ee272c4cb5aa92a5e7ee45c (diff) | |
| download | bundler-0c5d3b8c1f391aa5175321675ecd91ee6a1f231b.tar.gz | |
Auto merge of #6503 - koic:use_dir_instead_of_file_in_newgem_template, r=hsbt
Use `__dir__` instead of `__FILE__` in newgem.gemspec template
### What was the end-user problem that led to this PR?
Since Ruby 2.0 we've had `__dir__` as well as `__FILE__`.
The initial gem codes written with `bundle gem` using Ruby 2.0 or higher is an old description using `__FILE__`.
### What was your diagnosis of the problem?
Ruby 1.9 is EOL, so I think that there is not much Gem to start developed using it.
### What is your fix for the problem, implemented in this PR?
This PR uses `__dir__` when starting Gem development (i.e. `bundle gem`) using Ruby 2.0 or higher version.
Diffstat (limited to 'man/bundle-lock.ronn')
0 files changed, 0 insertions, 0 deletions