| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
For the `test-bundled-gems`, make `debug.so` with extconf.rb and
`make` command directly because `rake-compiler` assume ruby is
installed (but `test-bundled-gems` can run without installation).
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Remove GNU make `-O` and `-W` options which are short but followed
by an argument, so that `$mflags.set?(?n)` does not return `true`
wrongly.
|
| |
|
|
|
|
| |
[Bug #17476][ruby-core:101724]
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
To uniform directory structures, sometimes files are gathered in
different directory than the upstreams, executable files in
`libexec` for instance. Re-map these files to consistent with the
upstreams.
|
|
|
|
|
|
|
|
|
|
| |
Because unexpected names are listed in gemspec files.
* "Fix gemspec only case"
fc56b96b09e477686975c978142e3af9179219cd
* "Refined installation of gemspecs placed other than ext and lib"
31f4dec6373c15a58899f8b86e35d48a7d813bf6
|
|
|
|
|
|
|
|
| |
Use UnpackedInstaller for installation of default gems similarly it is
already used to install bundled gems.
This allows to reuse RubyGems functionality instead of custom code full
of exceptions.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Not to be overwritten by test-bundler-prepare. gem files often
contain useless gemspec files which have not been processed.
|
|
|
|
| |
did_you_mean splits the output by `$/`.
|
|
|
|
|
| |
As `spec.files` is used for `executables` and so on, the expanded
list needs to be located at the same place.
|
|
|
|
|
|
|
| |
Although gemspec file (e.g., power_assert and rake) often uses
`git ls-files`, as it does not make sense in other than its own
repository, it has been ignored now. Gather all files expanded
from the bundled gem to install, instead.
|
|
|
|
| |
Since 6f3e8df133c7785ff6bb6f18d1faec81fefb3999 in 2014.
|
| |
|
| |
|
| |
|
|
|
|
| |
Scripts to run the interpreter via debugger.
|
|
|
|
|
|
|
| |
These man pages are already in man format and assuming they are
mdoc format breaks things.
Fixes [Bug #16823]
|
|
|
|
|
| |
Should not overwrite ext/rubyvm/lib/forwardable/impl.rb by
lib/forwardable/impl.rb.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix incorrect calls to `Gem.ensure_gem_subdirectories`
This method doesn't take keyword args.
* Remove stuff no longer necessary
Now `Gem.ensure_gem_subdirectories` is doing its job, so some stuff is
no longer needed.
* Use the proper method for default gems
* Respect DESTDIR when creating rubygems folder layout
* Use `Gem.default_specifications_dir`
|
|
|
|
|
| |
The missing `\` in PR #2922 causes the default gems to be installed from
the .gem packages instead from the expanded sources.
|
|
|
|
|
| |
Simply use `File.basename` to remove the directory name (and
suffix), instead of `gsub` which can replace unintended parts.
|
|
|
|
|
| |
It is not necessary to strip the `destdir` prefix every iteration, when
it can be done just once.
|
|
|
|
| |
.gemspec files specifies not just `bin`, but also other directories.
|
|
|
|
|
|
| |
The local `path` variable does not provide any additional value and was
kept around just for clarity for easier review of the `extrac_files`
method move.
|
|
|
|
|
| |
This just gets the `RbInstall::DirPackage` closer by functionality to
`Gem::Package`.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rbinstall is using `$script_mode` and `$prog_mode`. However, the
`$script_mode` fallbacks to `$prog_mode` if not provided.
However, RubyGems do not distinguish between `$script_mode` and
`$prog_mode`:
https://github.com/rubygems/rubygems/blame/92892bbc3adba86a90756c385433835f6761b8da/lib/rubygems/installer.rb#L196
https://github.com/rubygems/rubygems/blame/92892bbc3adba86a90756c385433835f6761b8da/lib/rubygems/installer.rb#L515
https://github.com/rubygems/rubygems/blame/92892bbc3adba86a90756c385433835f6761b8da/lib/rubygems/installer.rb#L543
Comparing the usage of `$script_mode` and `$prog_mode`, it seems that
the `$script_mode` should be used where RubyGems expects `$prog_mode`.
|
|
|
|
|
|
|
|
| |
1. This is similar to what RubyGems does and it is less magic [[1]].
2. It avoids deprecated code paths in RubyGems [[2]].
[1]: https://github.com/rubygems/rubygems/blob/92892bbc3adba86a90756c385433835f6761b8da/lib/rubygems/installer.rb#L151
[2]: https://github.com/rubygems/rubygems/blob/92892bbc3adba86a90756c385433835f6761b8da/lib/rubygems/installer.rb#L187
|
|
|
|
|
|
| |
Extract bundled gems under ".bundle/gems" and get rid of
duplication which cause constant redefinition warnings at
`test-all` after `extract-gems` and `test-bundler`.
|
|
|
|
|
| |
It also needs to explicitly convert from String to Gem::Package
with initialization.
|
|
|
|
| |
to Gem::Package from String instance.
|
| |
|
|
|
|
|
| |
And revert "Relaxed warning assertions",
6f9be8505d172b110ec449478a791d70b9b74afb.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Compilation of extension libraries written in C++ are reportedly
broken due to https://github.com/ruby/ruby/pull/2404
The root cause of this issue was that the definition of ANYARGS
differ between C and C++, and that of C++ is incompatible with the
updated ones.
We are using the incompatibility against itself. In C++ two distinct
function prototypes can be overloaded. We provide the old, ANYARGSed
prototypes in addition to the current granular ones; and let the
older ones warn about types.
|
| |
|
|
|
|
|
| |
Even if they don't ship with any executables. This makes rbinstall
behaviour consistent with rubygems `gem install --default` command.
|
|
|
|
| |
For a certain editor which cannot handle here-document properly.
|