[ruby-core:124479] [Ruby Misc#21834] Extract `yaml/store` into it's own gem that depends on the `pstore` gem
Issue #21834 has been reported by postmodern (Hal Brodigan). ---------------------------------------- Misc #21834: Extract `yaml/store` into it's own gem that depends on the `pstore` gem https://bugs.ruby-lang.org/issues/21834 * Author: postmodern (Hal Brodigan) * Status: Open ---------------------------------------- Ruby 4.0.0 removed the `pstore` gem from the set of default stdlib libraries. However, `yaml/store` is still available from the `yaml` library, but relies on the `pstore` gem which is now no longer part of stdlib. It is odd that a file which is still part of stdlib requires another gem that is not part of stdlib. Perhaps `yaml/store` could be extracted into it's own gem called `yaml-store` which would have an explicit dependency on the `pstore` gem. This would reduce the need to explicitly list `pstore` as a gem dependency in the `Gemfile` or gemspec, if code requires `yaml/store` for `YAML::Store`. -- https://bugs.ruby-lang.org/
Issue #21834 has been updated by postmodern (Hal Brodigan). Note, while `pstore` is still available in Ruby 4.0.0 as a bundled gem, Bundler will refuse to load it unless it is explicitly listed in the `Gemfile` or gemspec. This means that if one's project uses any other gem which requires `yaml/store`, then `pstore` must be listed in the `Gemfile` or in one of the gem's gemspecs. Having an explicit `yaml-store` gem could reduce confusion. ---------------------------------------- Misc #21834: Extract `yaml/store` into it's own gem that depends on the `pstore` gem https://bugs.ruby-lang.org/issues/21834#change-116028 * Author: postmodern (Hal Brodigan) * Status: Open ---------------------------------------- Ruby 4.0.0 removed the `pstore` gem from the set of default stdlib libraries. However, `yaml/store` is still available from the `yaml` library, but relies on the `pstore` gem which is now no longer part of stdlib. It is odd that a file which is still part of stdlib requires another gem that is not part of stdlib. Perhaps `yaml/store` could be extracted into it's own gem called `yaml-store` which would have an explicit dependency on the `pstore` gem. This would reduce the need to explicitly list `pstore` as a gem dependency in the `Gemfile` or gemspec, if code requires `yaml/store` for `YAML::Store`. -- https://bugs.ruby-lang.org/
Issue #21834 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Open to Assigned Assignee set to hsbt (Hiroshi SHIBATA) ---------------------------------------- Misc #21834: Extract `yaml/store` into it's own gem that depends on the `pstore` gem https://bugs.ruby-lang.org/issues/21834#change-116063 * Author: postmodern (Hal Brodigan) * Status: Assigned * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- Ruby 4.0.0 removed the `pstore` gem from the set of default stdlib libraries. However, `yaml/store` is still available from the `yaml` library, but relies on the `pstore` gem which is now no longer part of stdlib. It is odd that a file which is still part of stdlib requires another gem that is not part of stdlib. Perhaps `yaml/store` could be extracted into it's own gem called `yaml-store` which would have an explicit dependency on the `pstore` gem. This would reduce the need to explicitly list `pstore` as a gem dependency in the `Gemfile` or gemspec, if code requires `yaml/store` for `YAML::Store`. -- https://bugs.ruby-lang.org/
participants (2)
-
hsbt (Hiroshi SHIBATA) -
postmodern (Hal Brodigan)