Oldest Gems by Date

Eric Hodel | Sun, 29 Aug 2010 08:38:30 GMT

This may be inaccurate because it trusts the gem specification, but the oldest 100 gems are:

Posted in Ruby, Rubygems | no comments

RubyGems 1.3.7

Eric Hodel | Fri, 14 May 2010 04:55:53 GMT

rubygems-update version 1.3.7 has been released!

• rubygems.org/

• docs.rubygems.org/

• rubygems.rubyforge.org/

• rubyforge.org/projects/rubygems

RubyGems is a package management framework for Ruby.

This gem is an update for the RubyGems software. You must have an installation of RubyGems before this update can be applied.

See Gem for information on RubyGems (or `ri Gem`)

To upgrade to the latest RubyGems, run:

  $ gem update --system  # you might need to be an administrator or root

NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no rubygems-update installed. You will need to use the following instructions if you see “Nothing to update”.

If you have an older version of RubyGems installed, then you can still do it in two steps:

  $ gem install rubygems-update  # again, might need to be admin/root
  $ update_rubygems              # ... here too

If you don’t have any RubyGems install, there is still the pre-gem approach to getting software, doing it manually:

1. Download from: rubyforge.org/frs/?group_id=126

2. Unpack into a directory and cd there

3. Install with: ruby setup.rb # you may need admin/root privilege

For more details and other options, see:

  ruby setup.rb --help

Changes

NOTE:

rubygems.org is now the default source for downloading gems.

You may have sources set via ~/.gemrc, so you should replace gems.rubyforge.org with rubygems.org

gems.rubyforge.org will continue to work for the forseeable future.

New features:

• `gem` commands

  • `gem install` and `gem fetch` now report alternate platforms when a matching one couldn’t be found.

  • `gem contents` —prefix is now the default as specified in —help. Bug #27211 by Mamoru Tasaka.

  • `gem fetch` can fetch of old versions again. Bug #27960 by Eric Hankins.

  • `gem query` and friends output now lists platforms. Bug #27856 by Greg Hazel.

  • `gem server` now allows specification of multiple gem dirs for documentation. Bug #27573 by Yuki Sonoda.

  • `gem unpack` can unpack gems again. Bug #27872 by Timothy Jones.

  • `gem unpack` now unpacks remote gems.

  • —user-install is no longer the default. If you really liked it, see Gem::ConfigFile to learn how to set it by default. (This change was made in 1.3.6)

• RubyGems now has platform support for IronRuby. Patch #27951 by Will Green.

Bug fixes:

• Require rubygems/custom_require if —disable-gem was set. Bug #27700 by Roger Pack.

• RubyGems now protects against exceptions being raised by plugins.

• rubygems/builder now requires user_interaction. Ruby Bug #1040 by Phillip Toland.

• Gem::Dependency support #version_requirements= with a warning. Fix for old Rails versions. Bug #27868 by Wei Jen Lu.

• Gem::PackageTask depends on the package dir like the other rake package tasks so dependencies can be hooked up correctly.

Posted in Ruby, Rubygems, Software | no comments

rubygems-isit19 1.0

Eric Hodel | Thu, 20 Aug 2009 05:26:00 GMT

• is it ruby 1.9?
• Documentation

Lets you figure out if your gems and gems you install might work on 1.9. Uses isitruby19.com as its datastore. Be sure to update the website with your experiences!

Features

• gem isit19 for checking your installed gems
• gem install plugin that tells you if your installed gem works on 1.9

Synopsis

$ gem install ZenTest

ZenTest 4.1.4 might work, 100% say 4.1.3 works on 1.9
Update http://isitruby19.com/ZenTest with your experiences!

Successfully installed ZenTest-4.1.4
1 gem installed

Posted in Rubygems, Software | no comments

A gemspec is not a big truck

Eric Hodel | Fri, 31 Jul 2009 22:48:56 GMT

It’s not something that you just dump something on. (paraphrasing)

There’s some terrible code that generates a ruby version of a Gem::Specification object.

This code is that it’s a broken implementation of Gem::Specification#to_ruby, a method that was documented all the way back to RubyGems 0.8.11.

Using this code generates a broken Gem::Specification object which will corrupt RubyGems indexes.

There are some projects in the wild that use this code, so if you own one of those, you should remove this code right away!

Remember! A gemspec is not a big truck!

Posted in Rubygems | no comments

RubyGems 1.3.5

Eric Hodel | Wed, 22 Jul 2009 00:37:47 GMT

RubyGems is a package management framework for Ruby.

See Gem for information on RubyGems (or `ri Gem`)

To upgrade to the latest RubyGems, run:

  $ gem update --system  # you might need to be an administrator or root

NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no rubygems-update installed. You will need to use the following instructions if you see “Nothing to update”.

If you have an older version of RubyGems installed, then you can still do it in two steps:

  $ gem install rubygems-update  # again, might need to be admin/root
  $ update_rubygems              # ... here too

If you don’t have any RubyGems install, there is still the pre-gem approach to getting software, doing it manually:

1. Download from: <a href=”http://rubyforge.org/frs/?group_id=126”>rubyforge.org/frs/?group_id=126
2. Unpack into a directory and cd there
3. Install with: ruby setup.rb # you may need admin/root privilege

For more details and other options, see:

  ruby setup.rb --help

Changes

Bug fixes:

• Fix use of prerelease gems.
• Gem.bin_path no longer escapes path with spaces. Bug #25935 and #26458.

Deprecation Notices:

• Bulk index update is no longer supported (the code currently remains, but not the tests)
• Gem::manage_gems was removed in 1.3.3.
• Time::today was removed in 1.3.3.

Posted in Rubygems, Software | 2 comments

RubyGems 1.3.4

Eric Hodel | Sat, 30 May 2009 14:20:00 GMT

NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no rubygems-update installed. You will need to follow the second set of update instructions if you see “Nothing to update”.

Release 1.3.4 fixes some bugs and adds some features.

Bug Fixes:

• Fixed various warnings
• Gem::ruby_version works correctly for 1.8 branch and trunk
• Prerelease gems now show up in `gem list` and can be used
• Fixed option name for `gem setup --format-executable`
• RubyGems now matches Ruby > 1.9.1 gem paths
• Gem::RemoteFetcher#download now works for explicit Windows paths across drives. Bug #25882 by Lars Christensen
• Fix typo in Gem::Requirement#parse. Bug #26000 by Mike Gunderloy.

Deprecation Notices:

• Bulk index update is no longer supported (the code currently remains, but not the tests)
• Gem::manage_gems was removed in 1.3.3.
• Time::today was removed in 1.3.3.

For a full list of changes to RubyGems and the contributor for each change, see the ChangeLog file.

How can I get RubyGems?

NOTE: If you have installed RubyGems using a package system you may want to install a new RubyGems through the same packaging system.

If you have a recent version of RubyGems (0.8.5 or later), then all you need to do is:

  $ gem update --system   (you might need to be admin/root)

NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no rubygems-update installed. You will need to follow the second set of update instructions if you see “Nothing to update”.

NOTE: You may have to run the command twice if you have any previosly installed rubygems-update gems.

If you have an older version of RubyGems installed, then you can still do it in two steps:

  $ gem install rubygems-update  (again, might need to be admin/root)
  $ update_rubygems              (... here too)

If you don’t have any gems install, there is still the pre-gem approach to getting software … doing it manually:

1. DOWNLOAD FROM: rubyforge.org/frs/?group_id=126
2. UNPACK INTO A DIRECTORY AND CD THERE
3. INSTALL WITH: ruby setup.rb (you may need admin/root privilege)

To File Bugs

The RubyGems bug tracker can be found on RubyForge at: rubyforge.org/tracker/?func=add&group_id=126&atid=575

When filing a bug, `gem env` output will be helpful in diagnosing the issue.

If you find a bug where RubyGems crashes, please provide debug output. You can do that with `gem —debug the_command`.

Thanks

Keep those gems coming!

— The RubyGems team

Posted in Rubygems, Software | no comments

A Project Naming Recommendation

Eric Hodel | Wed, 20 May 2009 23:08:02 GMT

I’ve gone through many different styles of project names, but I think I’ve finally found a naming scheme I like.

In the past, I’ve used class names with uppercase letters, dashed names and underscored names, and I think the underscores are the best for projects I’m packaging in ruby.

Rails solidified the convention of mapping CamelCase class names to underscored file names (class IMAPProcesor is defined in imap_processor.rb). Using underscored gem names makes it easy for people to figure out what file to require (same as the project name) or what class name to look for in ri.

If I have a plugin gem or an extension I’ll tack on the sub-project’s name with a dash. If I wanted to add a new handler for imap_to_rss for Chase bank email, the gem would be named imap_to_rss-chase.

This makes it easy to find in gem list -p and it conveniently namespaces the extension. It also would look nice with gems from github which break up author and project with a dash (drbrain-imap_to_rss-chase, if I used github). As an added bonus, when double-clicking any underscored part OS X only highlights a part of the name making cut-and-paste a little more convenient for picking apart gem names.

Currently almost 95% of gem names start with lowercase letters, 6% contain uppercase letters anywhere in the name, a little over 20% use dashes, 16% use underscore. Sixteen use both underscores and dashes (my favorite name being what_does_this_error_mean-merb).

Posted in Ruby, Rubygems | 2 comments

Fat binary gems

Eric Hodel | Tue, 12 May 2009 23:10:58 GMT

Right now people who publish native gems targeting the windows platform have a problem. Our problem is supporting ruby 1.8 and 1.9 at the same time. Right now, we can’t build one gem targeting 1.8 and one gem targeting 1.9, and have rubygems differentiate the two. I have a solution: fat binary gems. We can build a gem that contains dynamic libraries that target ruby 1.8 and ruby 1.9 on windows, with no changes to rubygems whatsoever. I’ve put together a proof of concept that I want to share. I will walk through the steps for building a fat binary gem with the tools we have today. The steps I am going to present are not necessarily the best steps, they are just the steps I took to get this idea working.

— Fat binary gems make the rockin’ world go round via Tender Love Making

Posted in Ruby, Rubygems | no comments

RubyGems 1.3.3

Eric Hodel | Mon, 04 May 2009 23:13:34 GMT

NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no rubygems-update installed. You will need to follow the second set of update instructions if you see “Nothing to update”.

Release 1.3.3 fixes some bugs and adds some features.

New Features:

• `gem server` allows port names (from /etc/services) with —port.
• `gem server` now has search that jumps to RDoc. Patch #22959 by Vladimir Dobriakov.
• `gem spec` can retrieve single fields from a spec (like `gem spec rake authors`).
• Gem::Specification#has_rdoc= is deprecated and ignored (defaults to true)
• RDoc is now generated regardless of Gem::Specification#has_rdoc?

Bug Fixes:

• `gem clean` now cleans up —user-install gems. Bug #25516 by Brett Eisenberg.
• Gem.bin_path now escapes paths with spaces.
• Rake extension builder uses explicit correctly loads rubygems when invoking rake.
• Prerelease versions now match “~>” correctly. Patch #25759 by Yossef Mendelssohn.
• Check bindir for executables, not root when validating. Bug reported by David Chelimsky.
• Remove Time.today, no way to override it before RubyGems loads. Bug #25564 by Emanuele Vicentini
• Raise Gem::Exception for #installation_path when not installed. Bug #25741 by Daniel Berger.
• Don’t raise in Gem::Specification#validate when homepage is nil. Bug #25677 by Mike Burrows.
• Uninstall executables from the correct directory. Bug #25555 by Brett Eisenberg.
• Raise Gem::LoadError if Kernel#gem fails due to previously-loaded gem. Bug reported by Alf Mikula.

Deprecation Notices:

• Gem::manage_gems has been removed.
• Time::today has been removed early. There was no way to make it warn and be easy to override with user code.

For a full list of changes to RubyGems and the contributor for each change, see the ChangeLog file.

How can I get RubyGems?

NOTE: If you have installed RubyGems using a package system you may want to install a new RubyGems through the same packaging system.

If you have a recent version of RubyGems (0.8.5 or later), then all you need to do is:

  $ gem update --system   (you might need to be admin/root)

NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no rubygems-update installed. You will need to follow the second set of update instructions if you see “Nothing to update”.

NOTE: You may have to run the command twice if you have any previosly installed rubygems-update gems.

If you have an older version of RubyGems installed, then you can still do it in two steps:

  $ gem install rubygems-update  (again, might need to be admin/root)
  $ update_rubygems              (... here too)

If you don’t have any gems install, there is still the pre-gem approach to getting software … doing it manually:

1. DOWNLOAD FROM: <a href=”http://rubyforge.org/frs/?group_id=126”>rubyforge.org/frs/?group_id=126
2. UNPACK INTO A DIRECTORY AND CD THERE
3. INSTALL WITH: ruby setup.rb (you may need admin/root privilege)

To File Bugs

Submit bugs on RubyForge at the <a href=”http://rubyforge.org/tracker/?func=add&group_id=126&atid=575”>RubyGems bug tracker

When filing a bug, `gem env` output will be helpful in diagnosing the issue.

If you find a bug where RubyGems crashes, please provide debug output. You can do that with `gem —debug the_command`.

Thanks

Keep those gems coming!

— The RubyGems team

Posted in Rubygems, Software | no comments

InfoQ on RubyGems Plugins

Eric Hodel | Thu, 23 Apr 2009 00:05:39 GMT

RubyGems 1.3.2 introduced a new feature: plugins that can hook into the install process and provide new commands. An example is Ryan Davis’ graph that visualizes dependencies between installed Gems. We talked to RubyGems maintainer Eric Hodel to learn more. By Mirko Stocker

— RubyGems Gets Plugins via InfoQ

Posted in Ruby, Rubygems | no comments