On Fri, Aug 22, 2008 at 2:49 PM, Seth Thomas Rasmussen
<[EMAIL PROTECTED]> wrote:
> So, I've been stuck for some weeks now. I had started doing Shoes with
> an r800something release, and at some point moved to "edge" builds.
> Things were generally working fine. Then, one day I clobbered my
> ~/.shoes/ to see the full behavior of my app when first getting setup.
> I did this because my app depends on a couple gems.
I write to you today to report about my affairs after having decided
to stop trying to fiddle with Shoes' RubyGems setup and instead figure
out why hpricot stopped installing properly through Shoes.setup for
me.
Because, you see, I *was* running along at first using
Shoes.setup { gem "twitter" }
and apparently Shoes was installing hpricot and things were working
fine. Somewhere along the line I wound up with the hpricot's
hpricot_scan extension failing to build and Shoes.setup just stalling
out.
Today I did: gem install -V hpricot
Here is the output: http://pastie.org/262235
I compared this to (in ~/.shoes/+gem/gems/hpricot): rake compile --trace
Here is that output: http://pastie.org/262241
I notice that the ragel tasks fail in both cases because I apparently
have no ragel command, but that a "normal" gem install seems to
succeed for hpricot regardless.
I am wondering if it is because of the way Shoes is using the gem
installer or rescuing exceptions that is causing my setup problems
with hpricot.
why, friends.. any feedback on that theory?
I just HAD to pick a gem that depends on Hpricot.. :P Maybe I'll try
another lib or even abandon this app in the interest of contuining to
actually build things. I am so very desparate to get my Shoes back on!
But I am frustrated by these problems and my lack of solving powers.
:(
--
Seth Thomas Rasmussen
http://greatseth.com
