RubyGems 0.3.0 and Rake -- comments and problems

Chad Fowler wrote:

>   * Install library "stub" allowing a normal 'require' to work (which 
> then does the rubygems require and 'require_gem'

Suggestion on above, you could actually do something interesting with 
this, if you could figure out the minimum required to generate the gem 
system.  You could actually set it up so the very basic require in a 
package if it hit one of these stubs would auto-install the gem system 
if it couldn't find it.  IE have some sort of gem bootstrap code, that 
could regenterate the gem system if it was lacking, assuming it's not 
just packaged with ruby anyway.

Anyways, comments on first running it, having not installed version .2. 
    I had also not installed rake before but figured I would use this 
chance to check it out.  gem -i rake worked fine, except it didn't run 
the actual rake installer, so there was no rake executable in my 
$HOME/usr/bin directory.  So I found out where it put it and ran install 
there so it put it all in the right places.  So then I ran rake on 
itself and it ran all it's tests successfully.  Ran the rake rdoc task 
and that failed as rdoc was missing 'rdoc/generators/template/html/css2'

This is was on a stable ruby install of ruby 1.8.1 (2004-04-27) 
[i686-linux].  Anyway, so I remembered there had been a rakefile for 
rubygems itself so I figured I would go back and play with that.  Typed 
rake and when it went through all it's tests it spit out:

   1) Failure:
test_garbled_gem_throws_format_exception(TestFormat) 
[./test/test_format.rb:29]:
<Gem::FormatException> exception expected but was
Class: <YAML::Error>
Message: <"Invalid object explicitly tagged !ruby/Object: 
\"rubygems_versionboom \\\"1.0\\\" nameboom testing versionboom 
!ruby/objectboomGemboomboomVersion versionboom 1.2.3 dateboom 2004-03-18 
22boom01boom52.859121 -05boom00 platformboom summaryboom This exercise 
the gem testing stuff. require_pathsboom - lib filesboom - lib/foo.rb - 
lib/test - lib/test.rb - lib/test/wow.rb autorequireboom test 
test_suite_fileboom foo requirementsboom - a computer processor\"">
---Backtrace---
/home/cec/s/c/cc1/usr/lib/ruby/1.8/yaml.rb:179:in `object_maker'
/home/cec/s/c/cc1/usr/lib/ruby/1.8/yaml/rubytypes.rb:36
/home/cec/s/c/cc1/usr/lib/ruby/1.8/yaml/rubytypes.rb:34:in `call'
../lib/rubygems/format.rb:92:in `transfer'
/home/cec/s/c/cc1/usr/lib/ruby/1.8/yaml.rb:39:in `load'
/home/cec/s/c/cc1/usr/lib/ruby/1.8/yaml.rb:39:in `load'
../lib/rubygems/format.rb:98:in `read_spec'
../lib/rubygems/format.rb:55:in `from_io'
../test/test_format.rb:31:in `test_garbled_gem_throws_format_exception'
../test/test_format.rb:29:in `assert_raise'
../test/test_format.rb:29:in `test_garbled_gem_throws_format_exception'

Anyhow, clearly there are a few issues, thought that I should let you 
folks know.  Does seem like they both do alot, but thought I would let 
the respective authors know about the issues inherant.

Looks like it's coming along though, keep it coming,

Charles Comstock