Beautiful, was able to install manually w/no errors! Thanks again for
all your help.

On Apr 10, 12:16 am, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote:
> Haml uses HTML comments in its documentation, which the RDoc parser
> chokes on. Installing the gem with --no-ri makes this go away.
>
> [EMAIL PROTECTED] wrote:
> > Well, I'm still not really sure what the problem with the rake task
> > is, but I was able to get far enough in the process to generate the
> > gem, but still bombed with the same no-method error. Here is the
> > relevant portion of the trace:
>
> > ......
> > ** Invoke Rakefile (first_time, not_needed)
> > ** Invoke init.rb (first_time, not_needed)
> > ** Invoke MIT-LICENSE (first_time, not_needed)
> > ** Invoke README.rdoc (first_time, not_needed)
> > ** Invoke VERSION (first_time, not_needed)
> > ** Execute pkg/haml-1.9.0.gem
> > WARNING:  no rubyforge_project specified
> > WARNING:  deprecated autorequire specified
> >   Successfully built RubyGem
> >   Name: haml
> >   Version: 1.9.0
> >   File: haml-1.9.0.gem
> > ** Execute gem
> > ** Execute package
> > ** Execute install
> > gem install --no-ri pkg/haml-1.9.0
> > rake aborted!
> > undefined method `exitstatus' for nil:NilClass
> > c:/ruby/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:899:in `sh'
> > c:/ruby/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:906:in `call'
> > c:/ruby/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:906:in `sh'
> > c:/ruby/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:985:in `sh'
> > D:/haml/rakefile:99
> > c:/ruby/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:546:in `call'
> > c:/ruby/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:546:in `execute'
> > c:/ruby/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:541:in `each'
> > c:/ruby/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:541:in `execute'
> > .....
>
> > After this point I saw that the gem had been generated, so I just did
> > a gem insall haml-1.9.0 --local and was able to install the gem and
> > confirm that all tests passed. However, the gem install threw an error
> > on the documentation, so maybe there is just some character in there
> > that doesn't play nice with windows. Here is the error from installing
> > the gem:
>
> > Installing ri documentation for haml-1.9.0...
> > ERROR:  While generating documentation for haml-1.9.0
> > ... MESSAGE:   Unhandled special: Special: type=17, text="<!-- This is
> > the peanu
> > tbutterjelly element -->"
> > ... RDOC args: --ri --op c:/ruby/lib/ruby/gems/1.8/doc/haml-1.9.0/ri --
> > title Ham
> > l --main README.rdoc --exclude lib/haml/buffer.rb --line-numbers --
> > inline-source
> >  --quiet lib MIT-LICENSE README.rdoc VERSION
> > (continuing with the rest of the installation)
> > Installing RDoc documentation for haml-1.9.0...
>
> > Thanks for all the help, hopefully this can be some help for anybody
> > else experiencing the same problems.
>
> > On Apr 9, 9:29 pm, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote:
>
> >> All versions of Haml maintain compatibility back to Rails 1.2.x (and
> >> maybe earlier).
>
> >> I'm not sure what's up with the zip stuff... you can safely comment that
> >> out, too. All you really need is the gem generation.
>
> >> - Nathan
>
> >> [EMAIL PROTECTED] wrote:
>
> >>> Actually, I just realized that there is no zip file in my pkg dir on
> >>> the git gem. Does the rake task remove the file after it unzips it?
>
> >>> On Apr 9, 9:09 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> >>> wrote:
>
> >>>> Thanks for the prompt response! That is kind of what I figured. So if
> >>>> I manage to get that gem installed, will it handle the older apps
> >>>> nicely, or will I be stuck needing different versions of haml for
> >>>> backwards compatibility?
>
> >>>> I commented those two lines out, and I'm now getting this error:
>
> >>>> D:\haml>rake install
> >>>> (in D:/haml)
> >>>> zip -r haml-1.9.0.zip haml-1.9.0
> >>>> rake aborted!
> >>>> undefined method `exitstatus' for nil:NilClass
>
> >>>> Not sure if that is the same error I got last night. Any ideas? I can
> >>>> post the full trace if you like as well.
>
> >>>> btw, absolutely love Haml & and especially Sass. Thanks for all the
> >>>> hard work!
>
> >>>> On Apr 9, 8:56 pm, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote:
>
> >>>>> Only git Haml maintains compatibility with edge Rails. You shouldn't
> >>>>> need tar to install it... all you need to do is install the gem with
> >>>>> rake install. You may also need to comment out the pkg.need_tar_gz and
> >>>>> pkg.need_tar_bz2 in the Rakefile.
>
> >>>>> [EMAIL PROTECTED] wrote:
>
> >>>>>> With haml 1.8.2 and a relatively recent version of edge rails and
> >>>>>> RSpec trunk, my specs crash with the following error:
>
> >>>>>> c:/ruby/lib/ruby/gems/1.8/gems/haml-1.8.2/lib/haml/template/plugin.rb:
> >>>>>> 42: undefined method `register_template_handler' for
> >>>>>> ActionView::Base:Class (NoMethodError)
>
> >>>>>> The template handler stuff has been moved to ActionView::Template, so
> >>>>>> I know the cause of the error, and by modifying the plugin.rb from the
> >>>>>> gem to use ActionView::Template instead all specs run fine. Only thing
> >>>>>> is that doing this in the gem is obviously not an ideal solution
> >>>>>> because I've also got apps frozen to versions of rails before that
> >>>>>> switch was made.
>
> >>>>>> So my question, is there any nice workaround for this? I thought about
> >>>>>> freezing the gem to the rails app, and making the change there, but it
> >>>>>> would be nice to not have to freeze haml everytime. I also tried to
> >>>>>> upgrade to haml 1.9 from github, but was unable to install from the
> >>>>>> gem because I'm on windows and it couldn't uncompress some .tar files.
>
> >>>>>> Appreciate any help you can provide!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/haml?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to