https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112018-12-04T09:30:48ZRuby Issue Tracking SystemRuby master - Bug #15376: Default gems: how will it work exactly?https://bugs.ruby-lang.org/issues/15376?journal_id=753932018-12-04T09:30:48Zshevegen (Robert A. Heiler)shevegen@gmail.com
<ul></ul><p>I can not answer most of these question due to my own lack of knowledge but I agree<br>
with mentioning it in NEWS and with some documentation - in particular I<br>
think the most important mention may be what happens, or what should happen,<br>
when there may be more than one version installed.</p>
<p>Most gems or possible all of them already have a .gemspec file as far as I know;<br>
at the least I remember that .gemspec files before have been written and<br>
added to ruby for the default gems provided there (is there any .gemspec still<br>
missing?).</p> Ruby master - Bug #15376: Default gems: how will it work exactly?https://bugs.ruby-lang.org/issues/15376?journal_id=754452018-12-06T06:18:46Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Assigned</i></li><li><strong>Assignee</strong> set to <i>hsbt (Hiroshi SHIBATA)</i></li></ul> Ruby master - Bug #15376: Default gems: how will it work exactly?https://bugs.ruby-lang.org/issues/15376?journal_id=755422018-12-10T07:13:39Znaruse (Yui NARUSE)naruse@airemix.jp
<ul><li><strong>Target version</strong> deleted (<del><i>2.6</i></del>)</li></ul> Ruby master - Bug #15376: Default gems: how will it work exactly?https://bugs.ruby-lang.org/issues/15376?journal_id=755892018-12-12T02:28:37Zhsbt (Hiroshi SHIBATA)hsbt@ruby-lang.org
<ul></ul><blockquote>
<ol>
<li>I believe we need to provide documentation for this. The NEWS file doesn't have much at all. The respective READMEs also have no relevant information and are misleading (see <a href="https://github.com/ruby/ostruct/pull/6" class="external">https://github.com/ruby/ostruct/pull/6</a>). I'll be glad to write an initial draft if need be, with the answers to the following questions...</li>
</ol>
</blockquote>
<p>I think so. But <code>default gems</code> is not introduced at Ruby 2.6. It's provided from Ruby 2.0.0. No one put its details and behavior as document into ruby repository.</p>
<p>I speak these behavior in RubyKaigi 2017 and RubyConf 2017.</p>
<p><a href="https://www.slideshare.net/hsbt/gemification-for-ruby-2530-82222826" class="external">https://www.slideshare.net/hsbt/gemification-for-ruby-2530-82222826</a></p>
<p>And I wrote the Japanese article of WEB+DB press.</p>
<p><a href="http://gihyo.jp/magazine/wdpress/archive/2018/vol103" class="external">http://gihyo.jp/magazine/wdpress/archive/2018/vol103</a></p>
<blockquote>
<ol start="2">
<li>Can we play with this right now? Maybe publishing prerelease versions of these libraries?</li>
</ol>
</blockquote>
<p>It's the maintainer's convenience. I or the maintainer should merge the latest stable versions into ruby core repository before the final releasing.</p>
<p>But rubygems.org protect namespace of the standard library contained default gems like this: <a href="https://rubygems.org/gems/digest" class="external">https://rubygems.org/gems/digest</a></p>
<p>We need to coordinate with rubygems.org team before publishing pre-release version of default gems. Fortunately, I got namespaces of default gems that will ship Ruby 2.6.</p>
<p><a class="user active user-mention" href="https://bugs.ruby-lang.org/users/182">@marcandre (Marc-Andre Lafortune)</a> Can you give the email address of rubygems.org? I grant you to owner of matrix and ostruct gems.</p>
<p>After that, Please release the stable versions of them to rubygems.org and backport them to ruby core repository.</p>
<blockquote>
<ol start="3">
<li>Has this been tested with Gemfile and gemspec, i.e. it will be possible to add a specification for one of these?</li>
</ol>
</blockquote>
<p>I'm not sure what mean <code>tested</code>. Can you describe it?</p>
<blockquote>
<ol start="4">
<li>What is supposed to happen if one does gem install ostruct in Ruby 2.5 (with current bundler, and with future bundler)?</li>
</ol>
</blockquote>
<p>The users can use ostruct gems same as 3rd party gems like rails or rspec from rubygems.org. But the users needs to specify <code>gem "ostruct", "0.1.0"</code> or Gemfile of Bundler.</p>
<blockquote>
<ol start="5">
<li>Will it be possible to use these in Gemfiles even with older Ruby (but recent bundler), so one could say gem 'ostruct' in a Gemfile and run bundle install in Ruby 2.5 without things exploding?</li>
</ol>
</blockquote>
<p>It's possible with RubyGems 2.x and 3.0. But it's not same as default gems installed by Ruby 2.6.0. Because <code>gem install foo --default</code> only install gemspec file. I didn't know why its behavior. But I'm working to change it with <a href="https://github.com/rubygems/rubygems/pull/2166" class="external">https://github.com/rubygems/rubygems/pull/2166</a></p>
<blockquote>
<ol start="6">
<li>Depending on 4/5, shouldn't we specify a required_rubygems_version and/or required_ruby_version in the gemspecs?</li>
</ol>
</blockquote>
<p>It's the maintainer's convenience. My personal opinion, We specify only supporting versions of Ruby like <code>>= 2.3</code> now.</p> Ruby master - Bug #15376: Default gems: how will it work exactly?https://bugs.ruby-lang.org/issues/15376?journal_id=759872018-12-29T18:27:45Zmarcandre (Marc-Andre Lafortune)marcandre-ruby-core@marc-andre.ca
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Closed</i></li></ul><p>Thank you for the answers. I've started improving the README for the matrix gem according to this info.</p> Ruby master - Bug #15376: Default gems: how will it work exactly?https://bugs.ruby-lang.org/issues/15376?journal_id=759882018-12-29T18:28:09Zmarcandre (Marc-Andre Lafortune)marcandre-ruby-core@marc-andre.ca
<ul><li><strong>Related to</strong> <i><a class="issue tracker-5 status-7 priority-4 priority-default closed" href="/issues/15486">Misc #15486</a>: Default gems README.md</i> added</li></ul>