Feature #13201
closedGemify dbm
Description
This issue is tracking for gem release of DBM module.
        
           Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
          Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
          
          
        
        
      
      - Related to Feature #5481: Gemifying Ruby standard library added
        
           Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
          Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
          
          
        
        
      
      - Status changed from Assigned to Closed
        
           Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
          Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
          
          
        
        
      
      - Status changed from Closed to Open
DBM gem is already registered. see. https://rubygems.org/gems/dbm
        
           Updated by shevegen (Robert A. Heiler) over 8 years ago
          Updated by shevegen (Robert A. Heiler) over 8 years 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.
        
           Updated by vo.x (Vit Ondruch) over 8 years ago
          Updated by vo.x (Vit Ondruch) over 8 years ago
          
          
        
        
      
      Since this is JRuby implementation of dbm, I believe it shouldn't be big big deal to get that name available ....
        
           Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
          Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
          
          
        
        
      
      Registered gem is here: https://github.com/jruby/dbm
I will coordinate JRuby team and rubygems admin.
        
           Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
          Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
          
          
        
        
      
      - Related to Feature #13248: Gemify gdbm added
        
           Updated by shyouhei (Shyouhei Urabe) over 8 years ago
          Updated by shyouhei (Shyouhei Urabe) over 8 years ago
          
          
        
        
      
      - Status changed from Open to Assigned
        
           Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
          Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
          
          
        
        
      
      - Status changed from Assigned to Closed
I shipped dbm gem implemented CRuby.
And update its gemspec on ruby core repository at r58314
        
           Updated by vo.x (Vit Ondruch) over 8 years ago
          Updated by vo.x (Vit Ondruch) over 8 years ago
          
          
        
        
      
      Could you please provide "Source Code" location information on rubygems.org? That would be helpful. Thx.
        
           Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
          Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
          
          
        
        
      
      vo.x (Vit Ondruch)
I update source code location in 1.0.0.beta1.