Ruby/AWS 0.3.3 Released

It’s only been a week since the release of Ruby/AWS 0.3.2, but 0.3.3 is here already.

Actually, there are almost no visible changes for the user. The only development of note is that the library is now available as a so-called gem for the RubyGems packaging system.

People have been on at me for years — basically, since RubyGems first became usable — to package my Ruby software as gems, but I’ve lacked the motivation to get to grips with a new packaging system.

It turns out that I overestimated the work involved. You can learn to create RubyGems in under an hour. The system is much less complex than building RPMs, for example. I really should have done this sooner.

This entry was posted in Ruby. Bookmark the permalink.

7 Responses to Ruby/AWS 0.3.3 Released

  1. garg says:

    Thanks for all your work on this!

    Just wondering, if I wanted to try this out on my Windows machine, where would I place the .amazonrc file?

    Thanks

  2. You know, you’re actually the first person to ask this.

    Where is the logical place for Ruby libs to look for system-wide config files on Windows? And for per-user config files?

    If you can let me know, I’ll add this functionality. In the meantime, look at line 53 in amazon.rb. This will enable you to make the change yourself, just to get it working in the meantime.

  3. I was wondering the same thing. I will manually config for now – but in windows, there are 2 spots I can see this config file going:

    1. %APPDATA% => C:\Documents and Settings\{username}\Application Data

    2. %USERPROFILE% => C:\Documents and Settings\{username}

    Maybe this helps…

  4. How does one figure out from within Ruby who {username} is? Is there a %USERNAME% or %USER% in Windows?

  5. Using %APPDATA% or %USERPROFILE% will automatically go to the {username} directory for whoever is logged in. So, you shouldn’t have to know the actual username – the other variables take care of it. On windows, just go Start -> Run and you can try this out. Type “%APPDATA%” and it will take you to the corresponding directory for the logged in user.

  6. Does that mean that I can just use ENV[‘APPDATA’] and ENV[‘USERPROFILE’] from within Ruby?

  7. Well, discussion on ruby-core about how to handle this issue leads me to the following conclusion.

    We’ll look for one of the following to be defined, in this order:

    ENV[‘HOME’]

    ENV[‘HOMEDRIVE’] + ENV[‘HOMEPATH’]

    ENV[‘USERPROFILE’]

    Expect to see this change in 0.4.1, due out soon.

Leave a Reply

Your email address will not be published. Required fields are marked *