# Rake 0.6.0 Released **URL:** \ **Category:** ruby-talk\ **Created:** [6 September 2005 00:44 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625 "2005-09-06T00:44:43Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Jim\_Weirich1](https://avatars.discourse-cdn.com/v4/letter/j/73ab20/32.png) [@Jim\_Weirich1](https://rubytalk.org/u/Jim_Weirich1)\ **Post date:** [6 September 2005 00:44 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/1 "2005-09-06T00:44:43Z")
= Rake 0.6.0 Released Its time for some long requested enhancements and lots of bug fixes ... And a whole new web page. == New Web Page The primary documentation for rake has moved from the RubyForge based wiki to its own Hieraki based web site. Constant spam on the wiki made it a difficult to keep clean. The new site will be easier to update and organize. Check out the new documentation at: [http://docs.rubyrake.org](http://docs.rubyrake.org) We will be adding new documentation to the site as time goes on. In addition to the new docs page, make sure you check out Martin Fowlers article on rake at [http://martinfowler.com/articles/rake.html](http://martinfowler.com/articles/rake.html) == Changes === New Features \* Multiple prerequisites on Rake rules now allowed. However, keep the   following in mind:   1. All the prerequisites of a rule must be available before a rule      is triggered, where "enabled" means (a) an existing file, (b) a      defined rule, or (c) another rule which also must be      trigger-able.   2. Rules are checked in order of definition, so it is important to      order your rules properly. If a file can be created by two      different rules, put the more specific rule first (otherwise the      more general rule will trigger first and the specific one will      never be triggered).   3. The \source\ method now returns the name of the first      prerequisite listed in the rule. \sources\ returns the      names of all the rule prerequisites, ordered as they are defined      in the rule. If the task has other prerequisites not defined in      the rule (but defined in an explicit task definition), then they      will \_not\_ be included in the sources list. \* FileLists may now use the egrep command. This popular enhancement   is now a core part of the FileList object. If you want to get a   list of all your to-dos, fixmes and TBD comments, add the following   to your Rakefile.     desc "Look for TODO and FIXME tags in the code"     task :todo do       FileList['\*\*/\*.rb'].egrep /#.\*(FIXME|TODO|TBD)/     end \* The \investigation\ method was added to task object to dump   out some important values. This makes it a bit easier to debug Rake   tasks.   For example, if you are having problems with a particular task, just   print it out:     task :huh do       puts Rake::Task['huh'].investigation     end \* The Rake::TestTask class now supports a "ruby\_opts" option to pass   arbitrary ruby options to a test subprocess. === Some Incompatibilities \* When using the \ruby\ command to start a Ruby subprocess, the   Ruby interpreter that is currently running rake is used by default.   This makes it easier to use rake in an environment with multiple   ruby installation. (Previously, the first ruby command found in the   PATH was used).   If you wish to chose a different Ruby interpreter, you can   explicitly choose the interpreter via the \sh\ command. \* The major rake classes (Task, FileTask, FileCreationTask, RakeApp)   have been moved out of the toplevel scope and are now accessible as   Rake::Task, Rake::FileTask, Rake::FileCreationTask and   Rake::Application. If your Rakefile   directly references any one of these tasks, you may:   1. Update your Rakefile to use the new classnames   2. Use the --classic-namespace option on the rake command to get the      old behavior,   3. Add \require 'rake/classic\_namespace'\ to the      Rakefile to get the old behavior.   \rake\ will print a rather annoying warning whenever a   deprecated class name is referenced without enabling classic   namespace. === Bug Fixes \* Several unit tests and functional tests were fixed to run better   under windows. \* Directory tasks are now a specialized version of a File task. A   directory task will only be triggered if it doesn't exist. It will   not be triggered if it is out of date w.r.t. any of its   prerequisites. \* Fixed a bug in the Rake::GemPackageTask class so that the gem now   properly contains the platform name. \* Fixed a bug where a prerequisite on a \file\ task would cause   an exception if the prerequisite did not exist. == What is Rake Rake is a build tool similar to the make program in many ways. But instead of cryptic make recipes, Rake uses standard Ruby code to declare tasks and dependencies. You have the full power of a modern scripting language built right into your build tool. == Availability The easiest way to get and install rake is via RubyGems ...   gem install rake (you may need root/admin privileges) Otherwise, you can get it from the more traditional places: Home Page:: [http://rake.rubyforge.org/](http://rake.rubyforge.org/) Download:: [http://rubyforge.org/project/showfiles.php?group\_id=50](http://rubyforge.org/project/showfiles.php?group_id=50) == Thanks As usual, it was input from users that drove a alot of these changes. The following people either contributed patches, made suggestions or made otherwise helpful comments. Thanks to ... \* Greg Fast (better ruby\_opt test options) \* Kelly Felkins (requested by better namespace support) \* Martin Fowler (suggested Task.investigation) \* Stuart Jansen (send initial patch for multiple prerequisites). \* Masao Mutch (better support for non-ruby Gem platforms) \* Philipp Neubeck (patch for file task exception fix) > **···** > > -- > -- Jim Weirich [jim@weirichhouse.org](mailto:jim@weirichhouse.org)[http://onestepback.org](http://onestepback.org) > ----------------------------------------------------------------- > "Beware of bugs in the above code; I have only proved it correct, > not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) ---
**Author:** ![Joel\_VanderWerf1](https://avatars.discourse-cdn.com/v4/letter/j/94ad74/32.png) [@Joel\_VanderWerf1](https://rubytalk.org/u/Joel_VanderWerf1)\ **Post date:** [6 September 2005 04:00 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/2 "2005-09-06T04:00:36Z")
Jim Weirich wrote: > = Rake 0.6.0 Released Trying to update my gems from 0.5.7, but I get this: $ gem update Upgrading installed gems... Updating Gem source index for: [http://gems.rubyforge.org](http://gems.rubyforge.org) Attempting remote upgrade of rake Attempting remote installation of 'rake' ERROR: While executing gem ... (Gem::Exception)     SSL is not installed on this system I do have libssl 0.9.7 installed, and the earlier rake installed ok. What could be causing this? > **···** > > -- >       vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407 ---
**Author:** ![Stu\_George](https://avatars.discourse-cdn.com/v4/letter/s/5e9695/32.png) [@Stu\_George](https://rubytalk.org/u/Stu_George)\ **Post date:** [6 September 2005 13:56 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/3 "2005-09-06T13:56:31Z")
hiya, a dumb question, what is the difference between rant and rake? they look the same? - Stu : Email via [xdi.org](http://public.xdi.org/=stu) > **···** > > On Tue, 6 Sep 2005 09:44:43 +0900, Jim Weirich \ wrote: > > > = Rake 0.6.0 Released > > > > Its time for some long requested enhancements and lots of bug fixes > > .. And a whole new web page. ---
**Author:** ![Christian\_Neukirche1](https://avatars.discourse-cdn.com/v4/letter/c/ee7513/32.png) [@Christian\_Neukirche1](https://rubytalk.org/u/Christian_Neukirche1)\ **Post date:** [6 September 2005 15:17 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/4 "2005-09-06T15:17:46Z")
Jim Weirich \ writes: > = Rake 0.6.0 Released > > Its time for some long requested enhancements and lots of bug fixes > ... And a whole new web page. Wonderful, and thank you for developing it. Since updating to 0.6.0, I have some problems with TestTask. This is the code that defines it:   desc "Run all the tests"   Rake::TestTask.new do |t|     t.libs \<\< "test"     t.test\_files = FileList['test\_\*.rb']     t.verbose = true     t.loader = XXX   end For various values of XXX: :rake results in:   /usr/local/bin/ruby -Ilib:test \     "/usr/local/lib/ruby/site\_ruby/1.8/rake/rake\_test\_loader.rb" \     "test\_dissident.rb" "test\_lifecycle.rb"   Loaded suite /usr/local/lib/ruby/site\_ruby/1.8/rake/rake\_test\_loader   Started   ...................   Finished in 0.277981 seconds.      19 tests, 116 assertions, 0 failures, 0 errors This is the method that works, but it shows the wrong "loaded suite". :testrb results in:   /usr/local/bin/ruby -Ilib:test "-S testrb \      /usr/local/lib/ruby/site\_ruby/1.8/rake/ruby182\_test\_unit\_fix.rb" \      "test\_dissident.rb" "test\_lifecycle.rb"   /usr/local/bin/ruby: invalid option - (-h will show valid options)   rake aborted! I don't know exactly whats happening here, but "testrb test\_\*.rb" works when called directly. For :direct, I get:   /usr/local/bin/ruby -Ilib:test "-e 'ARGV.each{|f| load f}'" \      "test\_dissident.rb" "test\_lifecycle.rb" And no further output. It works when I manually call   /usr/local/bin/ruby -e 'ARGV.each{|f| load f}' \     "test\_dissident.rb" "test\_lifecycle.rb" on the shell, though. The TestTask worked with my previous version of rake, which I think was 0.4.15. BTW, I think rake is a good tool every Ruby user benefits from, it would be great if it was included in future versions of the Ruby standard library. > **···** > > > -- Jim Weirich > > -- > Christian Neukirchen \ [http://chneukirchen.org](http://chneukirchen.org) ---
**Author:** ![Han\_Holl](https://avatars.discourse-cdn.com/v4/letter/h/d2c977/32.png) [@Han\_Holl](https://rubytalk.org/u/Han_Holl)\ **Post date:** [15 September 2005 10:11 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/5 "2005-09-15T10:11:48Z")
Hi Jim (and list), [cut] > Check out the new documentation at: [http://docs.rubyrake.org](http://docs.rubyrake.org) This site seems to be down (two days already) > \* The \investigation\ method was added to task object to dump > out some important values. This makes it a bit easier to debug Rake > tasks. Is there a reason not to call that inspect ? Cheers, Han Holl ---
**Author:** ![Jim\_Weirich1](https://avatars.discourse-cdn.com/v4/letter/j/73ab20/32.png) [@Jim\_Weirich1](https://rubytalk.org/u/Jim_Weirich1)\ **Post date:** [6 September 2005 04:47 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/6 "2005-09-06T04:47:46Z")
Sounds like a gem issue. The Rake gem is signed, but RubyGems is pretty careful about continuing even when the ssl libraries are not available. Try running the gem command with the --backtrace option so we can get a stacktrace and locate the code causing the error. > **···** > > On Tuesday 06 September 2005 12:00 am, Joel VanderWerf wrote: > > > I do have libssl 0.9.7 installed, and the earlier rake installed ok. > > What could be causing this? > > -- > -- Jim Weirich jim@weirichhouse.org [http://onestepback.org](http://onestepback.org) > ----------------------------------------------------------------- > "Beware of bugs in the above code; I have only proved it correct, > not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) ---
**Author:** ![Stefan\_Lang](https://avatars.discourse-cdn.com/v4/letter/s/e0b2c6/32.png) [@Stefan\_Lang](https://rubytalk.org/u/Stefan_Lang)\ **Post date:** [10 September 2005 18:38 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/7 "2005-09-10T18:38:16Z")
Sorry for replying so late. Generally, it's possible to convert a Rakefile to an Rantfile without much work. AFAIK Rant has all major features of Rake plus: \* Optional use of MD5 checksums instead of timestamps. \* Easy and portable tgz/zip file creation on Linux/MacOS X/Windows   (and probably most other platforms where ruby runs). \* Create a script, tailored to the needs of a project, which   can be used instead of an Rant installation   =\> Distribute this script with your project and users      and other developers don't need an Rant installation. \* It is possible to split up the build specification into   multiple files in different directories.   (=\> no such thing as "recursive make" necessary).   This feature will be highly improved with the next release. \* and a few more... Kind regards,   Stefan > **···** > > On Tuesday 06 September 2005 15:56, Stu George wrote: > > > On Tue, 6 Sep 2005 09:44:43 +0900, Jim Weirich \> \ \> \> wrote: > > \>= Rake 0.6.0 Released > > \> > > \>Its time for some long requested enhancements and lots of bug > > \> fixes .. And a whole new web page. > > > > hiya, a dumb question, what is the difference between rant and > > rake? they look the same? ---
**Author:** ![Jim\_Weirich1](https://avatars.discourse-cdn.com/v4/letter/j/73ab20/32.png) [@Jim\_Weirich1](https://rubytalk.org/u/Jim_Weirich1)\ **Post date:** [15 September 2005 12:04 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/8 "2005-09-15T12:04:33Z")
Sorry ... it seems that the database was wedged ... It is up and running again. > **···** > > On Thursday 15 September 2005 06:11 am, Han Holl wrote: > > > Hi Jim (and list), > > > > [cut] > > > > \> Check out the new documentation at: [http://docs.rubyrake.org](http://docs.rubyrake.org) > > > > This site seems to be down (two days already) > > -- > -- Jim Weirich jim@weirichhouse.org [http://onestepback.org](http://onestepback.org) > ----------------------------------------------------------------- > "Beware of bugs in the above code; I have only proved it correct, > not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) ---
**Author:** ![Joel\_VanderWerf1](https://avatars.discourse-cdn.com/v4/letter/j/94ad74/32.png) [@Joel\_VanderWerf1](https://rubytalk.org/u/Joel_VanderWerf1)\ **Post date:** [6 September 2005 05:21 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/9 "2005-09-06T05:21:22Z")
Jim Weirich wrote: > > I do have libssl 0.9.7 installed, and the earlier rake installed ok. > > What could be causing this? > > Sounds like a gem issue. The Rake gem is signed, but RubyGems is pretty > careful about continuing even when the ssl libraries are not available. > > Try running the gem command with the --backtrace option so we can get a > stacktrace and locate the code causing the error. $ gem update --backtrace Upgrading installed gems... Updating Gem source index for: [http://gems.rubyforge.org](http://gems.rubyforge.org) Attempting remote upgrade of rake Attempting remote installation of 'rake' ERROR: While executing gem ... (Gem::Exception)     SSL is not installed on this system /usr/local/lib/ruby/site\_ruby/1.8/rubygems/gem\_openssl.rb:21:in `ensure\_ssl\_available' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/package.rb:512:in `initialize' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/package.rb:481:in `each\_entry' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/package.rb:439:in `loop' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/package.rb:439:in `each\_entry' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/package.rb:424:in `each' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/package.rb:481:in `initialize' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/custom\_require.rb:21:in `new' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/custom\_require.rb:21:in `new' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/package.rb:580:in `open\_from\_io' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/package.rb:799:in `open\_from\_io' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/format.rb:53:in `from\_io' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/format.rb:41:in `from\_file\_by\_path' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/installer.rb:57:in `install' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/remote\_installer.rb:407:in `install' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/gem\_commands.rb:195:in `execute' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/gem\_commands.rb:153:in `each' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/gem\_commands.rb:153:in `execute' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/gem\_commands.rb:781:in `execute' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/gem\_commands.rb:777:in `each' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/gem\_commands.rb:777:in `execute' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/command.rb:49:in `invoke' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/cmd\_manager.rb:94:in `process\_args' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/cmd\_manager.rb:67:in `run' /usr/local/lib/ruby/site\_ruby/1.8/rubygems/gem\_runner.rb:13:in `run' /usr/local/bin/gem:17 > **···** > > > On Tuesday 06 September 2005 12:00 am, Joel VanderWerf wrote: > > -- >       vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407 ---
**Author:** ![Schlu\_Do](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@Schlu\_Do](https://rubytalk.org/u/Schlu_Do)\ **Post date:** [6 September 2005 12:31 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/10 "2005-09-06T12:31:27Z")
Hi, > Sounds like a gem issue. The Rake gem is signed, but RubyGems is pretty > careful about continuing even when the ssl libraries are not available. I got the same problem here on a Debian/MIPSel (a Buffalo LinkStation) box. SSL is installed, but I was missing the Ruby/SSL bindings. Doing an 'apt-get install libopenssl-ruby' did help (although it complained about the rdoc). On my Mac (10.4.2 Tiger) I didn't run into any problems with Ruby installed via DarwinPorts. Regards, Dominik. > **···** > > Jim Weirich \ wrote: ---
**Author:** ![stu3](https://avatars.discourse-cdn.com/v4/letter/s/7ea924/32.png) [@stu3](https://rubytalk.org/u/stu3)\ **Post date:** [12 September 2005 02:06 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/11 "2005-09-12T02:06:31Z")
Thanks for the reply. I only asked as I currently use rant, and I wondered since they seem so similar. the recursive thing / subdirs thing had some big bugs in the early 0.4.something bus 0.4.4 has been great so far.. didnt know about he md5 thing.. as I've hit a nasty rant timestamp bug that caused me to change the way I do a build on my current project. 😕 i better go look it up... -Stu ---
**Author:** ![Scott\_Mathieson1](https://avatars.discourse-cdn.com/v4/letter/s/f05b48/32.png) [@Scott\_Mathieson1](https://rubytalk.org/u/Scott_Mathieson1)\ **Post date:** [15 September 2005 12:17 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/12 "2005-09-15T12:17:40Z")
Can somebody please tell me how to unsubscribe from this list? ---
**Author:** ![Jim\_Weirich1](https://avatars.discourse-cdn.com/v4/letter/j/73ab20/32.png) [@Jim\_Weirich1](https://rubytalk.org/u/Jim_Weirich1)\ **Post date:** [6 September 2005 11:42 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/13 "2005-09-06T11:42:54Z")
Yeah, its the fact that the gem is signed and RubyGems is insisting on having SSL available. I think it should only do that if the security policy requires it, but that's a gems issue that needs looking into. So, what to do? (1) If you thought you had SSL, and you don't, then you probably should look into that. (2) If you want the latest rake no matter what, I put out an unsigned version of the gem on my betagem site labelled version 0.6.1. You can get it with:     gem install rake --source [http://onestepback.org/betagems](http://onestepback.org/betagems) > **···** > > On Tuesday 06 September 2005 01:21 am, Joel VanderWerf wrote: > > > Jim Weirich wrote: > > \> On Tuesday 06 September 2005 12:00 am, Joel VanderWerf wrote: > > \>\>I do have libssl 0.9.7 installed, and the earlier rake installed ok. > > \>\>What could be causing this? > > \> > > \> Sounds like a gem issue. The Rake gem is signed, but RubyGems is pretty > > \> careful about continuing even when the ssl libraries are not available. > > \> > > \> Try running the gem command with the --backtrace option so we can get a > > \> stacktrace and locate the code causing the error. > > -- > -- Jim Weirich jim@weirichhouse.org [http://onestepback.org](http://onestepback.org) > ----------------------------------------------------------------- > "Beware of bugs in the above code; I have only proved it correct, > not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) ---
**Author:** ![Stefan\_Lang](https://avatars.discourse-cdn.com/v4/letter/s/e0b2c6/32.png) [@Stefan\_Lang](https://rubytalk.org/u/Stefan_Lang)\ **Post date:** [12 September 2005 19:51 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/14 "2005-09-12T19:51:51Z")
> Thanks for the reply. I only asked as I currently use rant, and I > wondered since they seem so similar. > > the recursive thing / subdirs thing had some big bugs in the early > 0.4.something bus 0.4.4 has been great so far.. didnt know about > he md5 thing.. as I've hit a nasty rant timestamp bug that caused > me to change the way I do a build on my current project. 😕 Please write a bug report! If I can reproduce the bug, I can fix it for the next release. > i better go look it up... To use it, just put     import "md5" at the top of an Rantfile to use MD5 checksums instead of timestamps. Kind regards,   Stefan > **···** > > On Monday 12 September 2005 04:06, stu wrote: ---
**Author:** ![Brian\_Schroder1](https://avatars.discourse-cdn.com/v4/letter/b/2bfe46/32.png) [@Brian\_Schroder1](https://rubytalk.org/u/Brian_Schroder1)\ **Post date:** [19 September 2005 10:33 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/15 "2005-09-19T10:33:58Z")
> Can somebody please tell me how to unsubscribe from this list? From the ML Helpfile: > To unsubscribe ML \, send "unsubscribe" in the mail body > to the address \. hth, brian > **···** > > On 15/09/05, Scott Mathieson \ wrote: > > -- > [http://ruby.brian-schroeder.de/](http://ruby.brian-schroeder.de/) > > Stringed instrument chords: [http://chordlist.brian-schroeder.de/](http://chordlist.brian-schroeder.de/) ---
**Author:** ![Joel\_VanderWerf1](https://avatars.discourse-cdn.com/v4/letter/j/94ad74/32.png) [@Joel\_VanderWerf1](https://rubytalk.org/u/Joel_VanderWerf1)\ **Post date:** [7 September 2005 03:39 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/16 "2005-09-07T03:39:04Z")
Jim Weirich wrote: > Yeah, its the fact that the gem is signed and RubyGems is insisting on having > SSL available. I think it should only do that if the security policy > requires it, but that's a gems issue that needs looking into. > > So, what to do? > > (1) If you thought you had SSL, and you don't, then you probably should look > into that. That's it. My openssl.so was not installed correctly. It built ok in ext/openssl, but I had to disable the RUBYOPT=rubygems for it to install (and then gem update was able to install rake-0.6.0). With RUBYOPT=rubygems, I was getting this: $ make install /usr/local/lib/ruby/site\_ruby/1.8/rubygems/security.rb:18: uninitialized constant OpenSSL::Digest::SHA1 (NameError)         from /usr/local/lib/ruby/site\_ruby/1.8/rubygems.rb:397:in `require'         from /usr/local/lib/ruby/site\_ruby/1.8/rubygems.rb:397         from /usr/local/lib/ruby/site\_ruby/1.8/ubygems.rb:4:in `require'         from /usr/local/lib/ruby/site\_ruby/1.8/ubygems.rb:4 make: \*\*\* [/usr/local/lib/ruby/site\_ruby/1.8/i686-linux/openssl.so] Error 1 > **···** > > -- >       vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407 ---
**Author:** ![Jim\_Weirich1](https://avatars.discourse-cdn.com/v4/letter/j/73ab20/32.png) [@Jim\_Weirich1](https://rubytalk.org/u/Jim_Weirich1)\ **Post date:** [7 September 2005 04:04 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/17 "2005-09-07T04:04:06Z")
Thanks for the feedback. RubyGems assumes that if you can successfully require the openssl library, then ssl is available. Unfortunately, in the half installed state you were in, the openssl.so library was available but not the ruby portion (openssl.rb). So the require succeeded, fooling RubyGems into thinking the entire ssl infrastructure was in place when it was not. I'll put a fix in for that. > **···** > > On Tuesday 06 September 2005 11:39 pm, Joel VanderWerf wrote: > > > Jim Weirich wrote: > > \> Yeah, its the fact that the gem is signed and RubyGems is insisting on > > \> having SSL available. I think it should only do that if the security > > \> policy requires it, but that's a gems issue that needs looking into. > > \> > > \> So, what to do? > > \> > > \> (1) If you thought you had SSL, and you don't, then you probably should > > \> look into that. > > > > That's it. My openssl.so was not installed correctly. It built ok in > > ext/openssl, but I had to disable the RUBYOPT=rubygems for it to install > > (and then gem update was able to install rake-0.6.0). With > > RUBYOPT=rubygems, I was getting this: > > > > $ make install > > /usr/local/lib/ruby/site\_ruby/1.8/rubygems/security.rb:18: uninitialized > > constant OpenSSL::Digest::SHA1 (NameError) > >         from /usr/local/lib/ruby/site\_ruby/1.8/rubygems.rb:397:in `require' > >         from /usr/local/lib/ruby/site\_ruby/1.8/rubygems.rb:397 > >         from /usr/local/lib/ruby/site\_ruby/1.8/ubygems.rb:4:in `require' > >         from /usr/local/lib/ruby/site\_ruby/1.8/ubygems.rb:4 > > make: \*\*\* [/usr/local/lib/ruby/site\_ruby/1.8/i686-linux/openssl.so] Error 1 > > -- > -- Jim Weirich jim@weirichhouse.org [http://onestepback.org](http://onestepback.org) > ----------------------------------------------------------------- > "Beware of bugs in the above code; I have only proved it correct, > not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) ---
**Author:** ![Chris\_Martin](https://avatars.discourse-cdn.com/v4/letter/c/df705f/32.png) [@Chris\_Martin](https://rubytalk.org/u/Chris_Martin)\ **Post date:** [7 September 2005 19:33 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/18 "2005-09-07T19:33:41Z")
To clarify for the slow and/or nubys who might get this error when installing and/or updating gems for rails. The ruby openssl library needs to be installed. eg, debian needs libopenssl-ruby1.8 May be the error could be made clearer, I was sitting there going, "but it IS installed!" in much more expletive words. 😉 I even read this thread last night, but your explanation didn't click until I double checked it today. > **···** > > On 9/7/05, Jim Weirich \ wrote: > > > On Tuesday 06 September 2005 11:39 pm, Joel VanderWerf wrote: > > \> Jim Weirich wrote: > > \> \> Yeah, its the fact that the gem is signed and RubyGems is insisting on > > \> \> having SSL available. I think it should only do that if the security > > \> \> policy requires it, but that's a gems issue that needs looking into. > > \> \> > > \> \> So, what to do? > > \> \> > > \> \> (1) If you thought you had SSL, and you don't, then you probably should > > \> \> look into that. > > \> > > \> That's it. My openssl.so was not installed correctly. It built ok in > > \> ext/openssl, but I had to disable the RUBYOPT=rubygems for it to install > > \> (and then gem update was able to install rake-0.6.0). With > > \> RUBYOPT=rubygems, I was getting this: > > \> > > \> $ make install > > \> /usr/local/lib/ruby/site\_ruby/1.8/rubygems/security.rb:18: uninitialized > > \> constant OpenSSL::Digest::SHA1 (NameError) > > \> from /usr/local/lib/ruby/site\_ruby/1.8/rubygems.rb:397:in `require' > > \> from /usr/local/lib/ruby/site\_ruby/1.8/rubygems.rb:397 > > \> from /usr/local/lib/ruby/site\_ruby/1.8/ubygems.rb:4:in `require' > > \> from /usr/local/lib/ruby/site\_ruby/1.8/ubygems.rb:4 > > \> make: \*\*\* [/usr/local/lib/ruby/site\_ruby/1.8/i686-linux/openssl.so] Error 1 > > > > Thanks for the feedback. RubyGems assumes that if you can successfully > > require the openssl library, then ssl is available. Unfortunately, in the > > half installed state you were in, the openssl.so library was available but > > not the ruby portion (openssl.rb). So the require succeeded, fooling > > RubyGems into thinking the entire ssl infrastructure was in place when it was > > not. > > > > I'll put a fix in for that. > > > > -- > > -- Jim Weirich jim@weirichhouse.org [http://onestepback.org](http://onestepback.org) > > ----------------------------------------------------------------- > > "Beware of bugs in the above code; I have only proved it correct, > > not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) > > -- > Chris Martin > Web Developer > Open Source & Web Standards Advocate > > > **[Chriscodes.com is for sale | HugeDomains](https://www.hugedomains.com/domain_profile.cfm?d=chriscodes.com)** > > > > Painless, quick delivery of your domain name. Fast and professional service. ---
**Author:** ![Joel\_VanderWerf1](https://avatars.discourse-cdn.com/v4/letter/j/94ad74/32.png) [@Joel\_VanderWerf1](https://rubytalk.org/u/Joel_VanderWerf1)\ **Post date:** [7 September 2005 22:22 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/19 "2005-09-07T22:22:21Z")
Chris Martin wrote: ... > To clarify for the slow and/or nubys who might get this error when > installing and/or updating gems for rails. > > The ruby openssl library needs to be installed. eg, debian needs > libopenssl-ruby1.8 If you're not using packages and are building ruby from source, you can do export RUBYOPT= in your shell before building ruby. Then, if you have openssl installed (not the ruby binding--the real openssl lib), the ruby openssl extension in the ext/ dir will build and install. Then you can have export RUBYOPT=rubygems or whatever. But I think Jim's fix to RubyGems will get around this entirely. > **···** > > -- >       vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407 ---
**Author:** ![Jim\_Weirich1](https://avatars.discourse-cdn.com/v4/letter/j/73ab20/32.png) [@Jim\_Weirich1](https://rubytalk.org/u/Jim_Weirich1)\ **Post date:** [7 September 2005 22:37 UTC](https://rubytalk.org/t/rake-0-6-0-released/20625/20 "2005-09-07T22:37:44Z")
Joel VanderWerf said: > Chris Martin wrote: > ... > > > To clarify for the slow and/or nubys who might get this error when > > installing and/or updating gems for rails. > > > > The ruby openssl library needs to be installed. eg, debian needs > > libopenssl-ruby1.8 > > If you're not using packages and are building ruby from source, you can do > > export RUBYOPT= > > in your shell before building ruby. Then, if you have openssl installed > (not the ruby binding--the real openssl lib), the ruby openssl extension > in the ext/ dir will build and install. Then you can have > > export RUBYOPT=rubygems > > or whatever. > > But I think Jim's fix to RubyGems will get around this entirely. The patch in RubyGems CVS will address this exact problem. We still need to fix the gem command so that it can install signed gems without SSL installed ... but I don't think that will be a hard problem. > **···** > > -- > -- Jim Weirich jim@weirichhouse.org [http://onestepback.org](http://onestepback.org) > ----------------------------------------------------------------- > "Beware of bugs in the above code; I have only proved it correct, > not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)