Project

General

Profile

Feature #13201

Gemify dbm

Added by hsbt (Hiroshi SHIBATA) 8 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Target version:
[ruby-core:79479]

Description

This issue is tracking for gem release of DBM module.


Related issues

Related to Ruby trunk - Feature #5481: Gemifying Ruby standard libraryAssigned
Related to Ruby trunk - Feature #13248: Gemify gdbmAssigned

Associated revisions

Revision 57577
Added by hsbt (Hiroshi SHIBATA) 8 months ago

Added initial gemspec for DBM module.

[Feature #13201]

History

#1 Updated by hsbt (Hiroshi SHIBATA) 8 months ago

  • Related to Feature #5481: Gemifying Ruby standard library added

#2 Updated by hsbt (Hiroshi SHIBATA) 8 months ago

  • Status changed from Assigned to Closed

Applied in changeset r57577.


Added initial gemspec for DBM module.

[Feature #13201]

#3 [ruby-core:79512] Updated by hsbt (Hiroshi SHIBATA) 7 months ago

  • Status changed from Closed to Open

DBM gem is already registered. see. https://rubygems.org/gems/dbm

#4 [ruby-core:79789] Updated by shevegen (Robert A. Heiler) 7 months ago

Perhaps the rubygems.org folks can de-register that gem, due to two reasons - ruby stdlib and core should have a higher priority over custom gems; and the gem is not very active, only two updates, one in 2009 and another one in 2013. (It seems to be jruby specific. Perhaps it could actually be integrated into jruby itself as-is.)

In the long run, optional namespaces/authorship-registries for gems should perhaps be added (and multiple same-named gems could be made available at rubygems.org, though of course then gem also needs a way to install same-named gems from different authors). All gems in ruby stdlib etc.. could have a registry such as "ruby core" or some similar identifier to keep track of the gems that are currently available, at the least in the latest ruby release; the gem commandline interface should then be able to pick up that information and notify the user of possible name conflicts. But anyway I digress - IMO ruby core should have priority over other gems at all times.

#5 [ruby-core:79790] Updated by vo.x (Vit Ondruch) 7 months ago

Since this is JRuby implementation of dbm, I believe it shouldn't be big big deal to get that name available ....

#6 [ruby-core:79793] Updated by hsbt (Hiroshi SHIBATA) 7 months ago

Registered gem is here: https://github.com/jruby/dbm

I will coordinate JRuby team and rubygems admin.

#7 Updated by hsbt (Hiroshi SHIBATA) 7 months ago

#8 Updated by shyouhei (Shyouhei Urabe) 5 months ago

  • Status changed from Open to Assigned

#9 [ruby-core:80967] Updated by hsbt (Hiroshi SHIBATA) 5 months ago

  • Status changed from Assigned to Closed

I shipped dbm gem implemented CRuby.

https://rubygems.org/gems/dbm

And update its gemspec on ruby core repository at r58314

#10 [ruby-core:80980] Updated by vo.x (Vit Ondruch) 5 months ago

Could you please provide "Source Code" location information on rubygems.org? That would be helpful. Thx.

#11 [ruby-core:81120] Updated by hsbt (Hiroshi SHIBATA) 5 months ago

vo.x (Vit Ondruch)

I update source code location in 1.0.0.beta1.

Also available in: Atom PDF