[ruby-core:90274] [Ruby trunk Bug#15376] Default gems: how will it work exactly?

[ruby-core:90274] [Ruby trunk Bug#15376] Default gems: how will it work exactly?

[ruby-core]

Issue #15376 has been reported by marcandre (Marc-Andre Lafortune).

----------------------------------------
Bug #15376: Default gems: how will it work exactly?
https://bugs.ruby-lang.org/issues/15376

* Author: marcandre (Marc-Andre Lafortune)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 2.6
* ruby -v: 
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
Some standard libraries will be gemified in Ruby 2.6+.

1) 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 https://github.com/ruby/ostruct/pull/6). I'll be glad to write an initial draft if need be, with the answers to the following questions...

2) Can we play with this right now? Maybe publishing prelease versions of these libraries?

3) Has this been tested with `Gemfile` and  `gemspec`, i.e. it will be possible to add a specification for one of these?

4) What is supposed to happen if one does `gem install ostruct` in Ruby 2.5 (with current bundler, and with future bundler)? 

5) Will it be possible to use these in `Gemfile`s 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?

6) Depending on 4/5, shouldn't we specify a ` required_rubygems_version` and/or ` required_ruby_version` in the gemspecs?




-- 
https://bugs.ruby-lang.org/

[ruby-core:90281] [Ruby trunk Bug#15376] Default gems: how will it work exactly?

[shevegen]

Issue #15376 has been updated by shevegen (Robert A. Heiler).


I can not answer most of these question due to my own lack of knowledge but I agree
with mentioning it in NEWS and with some documentation - in particular I
think the most important mention may be what happens, or what should happen,
when there may be more than one version installed.

Most gems or possible all of them already have a .gemspec file as far as I know;
at the least I remember that .gemspec files before have been written and
added to ruby for the default gems provided there (is there any .gemspec still
missing?).

----------------------------------------
Bug #15376: Default gems: how will it work exactly?
https://bugs.ruby-lang.org/issues/15376#change-75393

* Author: marcandre (Marc-Andre Lafortune)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 2.6
* ruby -v: 
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
Some standard libraries will be gemified in Ruby 2.6+.

1) 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 https://github.com/ruby/ostruct/pull/6). I'll be glad to write an initial draft if need be, with the answers to the following questions...

2) Can we play with this right now? Maybe publishing prelease versions of these libraries?

3) Has this been tested with `Gemfile` and  `gemspec`, i.e. it will be possible to add a specification for one of these?

4) What is supposed to happen if one does `gem install ostruct` in Ruby 2.5 (with current bundler, and with future bundler)? 

5) Will it be possible to use these in `Gemfile`s 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?

6) Depending on 4/5, shouldn't we specify a ` required_rubygems_version` and/or ` required_ruby_version` in the gemspecs?




-- 
https://bugs.ruby-lang.org/

[ruby-core:90334] [Ruby trunk Bug#15376][Assigned] Default gems: how will it work exactly?

[mame]

Issue #15376 has been updated by mame (Yusuke Endoh).

Status changed from Open to Assigned
Assignee set to hsbt (Hiroshi SHIBATA)

----------------------------------------
Bug #15376: Default gems: how will it work exactly?
https://bugs.ruby-lang.org/issues/15376#change-75445

* Author: marcandre (Marc-Andre Lafortune)
* Status: Assigned
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
* Target version: 2.6
* ruby -v: 
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
Some standard libraries will be gemified in Ruby 2.6+.

1) 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 https://github.com/ruby/ostruct/pull/6). I'll be glad to write an initial draft if need be, with the answers to the following questions...

2) Can we play with this right now? Maybe publishing prelease versions of these libraries?

3) Has this been tested with `Gemfile` and  `gemspec`, i.e. it will be possible to add a specification for one of these?

4) What is supposed to happen if one does `gem install ostruct` in Ruby 2.5 (with current bundler, and with future bundler)? 

5) Will it be possible to use these in `Gemfile`s 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?

6) Depending on 4/5, shouldn't we specify a ` required_rubygems_version` and/or ` required_ruby_version` in the gemspecs?




-- 
https://bugs.ruby-lang.org/

[ruby-core:90434] [Ruby trunk Bug#15376] Default gems: how will it work exactly?

[hsbt]

Issue #15376 has been updated by hsbt (Hiroshi SHIBATA).


>1) 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 https://github.com/ruby/ostruct/pull/6). I'll be glad to write an initial draft if need be, with the answers to the following questions...

I think so. But `default gems` 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.

I speak these behavior in RubyKaigi 2017 and RubyConf 2017.

https://www.slideshare.net/hsbt/gemification-for-ruby-2530-82222826

And I wrote the Japanese article of WEB+DB press.

http://gihyo.jp/magazine/wdpress/archive/2018/vol103

>2) Can we play with this right now? Maybe publishing prerelease versions of these libraries?

It's the maintainer's convenience. I or the maintainer should merge the latest stable versions into ruby core repository before the final releasing.

But rubygems.org protect namespace of the standard library contained default gems like this: https://rubygems.org/gems/digest

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.

@marcandre Can you give the email address of rubygems.org? I grant you to owner of matrix and ostruct gems.

After that, Please release the stable versions of them to rubygems.org and backport them to ruby core repository.

>3) Has this been tested with Gemfile and gemspec, i.e. it will be possible to add a specification for one of these?

I'm not sure what mean `tested`. Can you describe it?

>4) What is supposed to happen if one does gem install ostruct in Ruby 2.5 (with current bundler, and with future bundler)?

The users can use ostruct gems same as 3rd party gems like rails or rspec from rubygems.org. But the users needs to specify `gem "ostruct", "0.1.0"` or Gemfile of Bundler.

>5) 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?

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 `gem install foo --default` only install gemspec file. I didn't know why its behavior. But I'm working to change it with https://github.com/rubygems/rubygems/pull/2166

>6) Depending on 4/5, shouldn't we specify a required_rubygems_version and/or required_ruby_version in the gemspecs?

It's the maintainer's convenience. My personal opinion, We specify only supporting versions of Ruby like `>= 2.3` now.


----------------------------------------
Bug #15376: Default gems: how will it work exactly?
https://bugs.ruby-lang.org/issues/15376#change-75589

* Author: marcandre (Marc-Andre Lafortune)
* Status: Assigned
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
* Target version: 
* ruby -v: 
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
Some standard libraries will be gemified in Ruby 2.6+.

1) 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 https://github.com/ruby/ostruct/pull/6). I'll be glad to write an initial draft if need be, with the answers to the following questions...

2) Can we play with this right now? Maybe publishing prelease versions of these libraries?

3) Has this been tested with `Gemfile` and  `gemspec`, i.e. it will be possible to add a specification for one of these?

4) What is supposed to happen if one does `gem install ostruct` in Ruby 2.5 (with current bundler, and with future bundler)? 

5) Will it be possible to use these in `Gemfile`s 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?

6) Depending on 4/5, shouldn't we specify a ` required_rubygems_version` and/or ` required_ruby_version` in the gemspecs?




-- 
https://bugs.ruby-lang.org/

[ruby-core:90811] [Ruby trunk Bug#15376][Closed] Default gems: how will it work exactly?

[ruby-core]

Issue #15376 has been updated by marcandre (Marc-Andre Lafortune).

Status changed from Assigned to Closed

Thank you for the answers. I've started improving the README for the matrix gem according to this info.

----------------------------------------
Bug #15376: Default gems: how will it work exactly?
https://bugs.ruby-lang.org/issues/15376#change-75987

* Author: marcandre (Marc-Andre Lafortune)
* Status: Closed
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
* Target version: 
* ruby -v: 
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
Some standard libraries will be gemified in Ruby 2.6+.

1) 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 https://github.com/ruby/ostruct/pull/6). I'll be glad to write an initial draft if need be, with the answers to the following questions...

2) Can we play with this right now? Maybe publishing prelease versions of these libraries?

3) Has this been tested with `Gemfile` and  `gemspec`, i.e. it will be possible to add a specification for one of these?

4) What is supposed to happen if one does `gem install ostruct` in Ruby 2.5 (with current bundler, and with future bundler)? 

5) Will it be possible to use these in `Gemfile`s 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?

6) Depending on 4/5, shouldn't we specify a ` required_rubygems_version` and/or ` required_ruby_version` in the gemspecs?




-- 
https://bugs.ruby-lang.org/