ar_mailer 1.4.0
Eric Hodel | Wed, 24 Jun 2009 22:53:06 GMT
ar_mailer is a two-phase delivery agent for ActionMailer. Even delivering email to the local machine may take too long when you have to send hundreds of messages. ar_mailer allows you to store messages into the database for later delivery by a separate process, ar_sendmail.
Changes:
- 1.8.7 and 1.9 STARTTLS compatibility, now uses smtp_tls gem for STARTTLS on 1.8.6
- Fix 1.9 warnings
production_log_analyzer 1.5.1
Eric Hodel | Wed, 24 Jun 2009 03:44:37 GMT
production_log_analyzer version 1.5.1 has been released!
- <a href=”http://seattlerb.rubyforge.org/production_log_analyzer”>Documentation
- <a href=”http://rubyforge.org/projects/seattlerb”>Project page
- <a href=”http://rubyforge.org/tracker/?func=add&group_id=1513&atid=5921”>Bug reports
production_log_analyzer lets you find out which actions on a Rails site are slowing you down.
Changes:
- 1.9 and 1.8.7 compatibility.
Converting from REXML to Nokogiri
Eric Hodel | Thu, 18 Jun 2009 01:02:02 GMT
Nokogiri is pretty darn cool, certainly far cooler than REXML. I switched UPnP to Nokogiri, and here’s a handy guide.
require 'rexml/document'
Becomes
require 'nokogiri'
REXML::Document.new
Becomes
Nokogiri::XML
Both accept String or IO objects
my_element.element['element/path']
Becomes
my_element.at 'element > path'
You can use CSS in #at
my_element.each_element 'element/path' do |sub_element|
Becomes
my_element.xpath('./xmlns:element/xmlns:path').each do |sub_element|
”.” is used to select sub-elements of this one
See also Nokogiri’s Node documentation.
UPnP 1.2.0
Eric Hodel | Wed, 17 Jun 2009 00:06:07 GMT
An implementation of the UPnP protocol
Changes
- 2 minor enhancements
- Workaround for missing socket constants on Windows. Reported by Yuri.
- upnp_discover now shows action argument and return value names.
- 4 bug fixes
- Method name must not include entire URI. Reported by Ian Macdonald.
- Step in allowedValueRange is optional. Reported by Ian Macdonald.
- upnp_listen works with all notification types. Reported by Ian Macdonald.
- upnp_discover now warns when a device failed to instantiate. Reported by Ian Macdonald.
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:
- DOWNLOAD FROM: rubyforge.org/frs/?group_id=126
- UNPACK INTO A DIRECTORY AND CD THERE
- 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
orca_card 1.0
Eric Hodel | Tue, 19 May 2009 18:54:33 GMT
orca_card version 1.0 has been released!
Dumps information about your ORCA card. ORCA cards are Western Washington’s all-in-one transit smart card that allow travel via bus, train and ferry throughout King, Kitsap, Snohomish and Pierce counties.
NOTE: This is a cheap hack, patches wanted
imap_processor 1.1
Eric Hodel | Mon, 18 May 2009 22:56:00 GMT
imap_processor version 1.1 has been released!
IMAPProcessor is a client for processing messages on an IMAP server. It provides some basic mechanisms for connecting to an IMAP server, determining capabilities and handling messages.
IMAPProcessor ships with the imap_keywords executable which can query an IMAP server for keywords set on messages in mailboxes.
Changes:
- 1 minor enhancement
- IMAPProcessor#each_message allows messages to be omitted from the returned uid list (skipped)
imap_to_rss 1.0
Eric Hodel | Fri, 15 May 2009 18:17:00 GMT
imap_to_rss version 1.0 has been released!
IMAPToRSS turns messages on an IMAP server into RSS entries when the match a handler. Included handlers work for email from Amazon, HSBC and UPS. IMAPToRSS automatically loads handlers for any other mail.
imap_processor 1.0
Eric Hodel | Wed, 13 May 2009 03:14:00 GMT
imap_processor version 1.0 has been released!
IMAPProcessor is a client for processing messages on an IMAP server. It provides some basic mechanisms for connecting to an IMAP server, determining capabilities and handling messages.
IMAPProcessor ships with the imap_keywords executable which can query an IMAP server for keywords set on messages in mailboxes.
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:
- DOWNLOAD FROM: <a href=”http://rubyforge.org/frs/?group_id=126”>rubyforge.org/frs/?group_id=126
- UNPACK INTO A DIRECTORY AND CD THERE
- 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

Articles