Hi Michael,

I think the issue is that when using a bundled merb-core that's not
recent (as 0.9.9 indicates), you're at risk of running code that might
contain bugs or incompatibilities. Unfortunately there's no way around
this, except for waiting until 1.0 is out. Each development in
merb.thor is coupled to the latest Merb version; that's why you can
keep tasks/merb.thor under version control simultaneously with your
app.

At the moment people having issues with merb.thor ar usually bitten by
two things:
- required gem version mismatches with config/dependencies.rb
- running code that's not up-to-date with the current development
release (RC 2 atm)

Could you see if it helps to update to RC2?

- Fabien

ps. adding a load path (gem load path) is a matter of
Gem.path.unshift(yourpath)

On Oct 25, 11:15 am, "Michael Fairchild" <[EMAIL PROTECTED]>
wrote:
> Hello,
>   Alright, perhaps I am missing something obvious, but I don't understand
> why I can't seem to load frozen gems.  I am using ./bin/merb.  ./gems/ is in
> my load path, but I still get errors about not having the gems available,
> even tho they are there.
> Am I missing something?
> below are a few commands to illustrate the problem:
> <code>
> [EMAIL PROTECTED]:~/WebApps/appname/releases/20081025085933$ ./bin/merb
> Loading init file from
> /home/fairchild/WebApps/appname/releases/20081025085933/config/init.rb
> Loading
> /home/fairchild/WebApps/appname/releases/20081025085933/config/environments 
> /development.rb
>  ~ Loaded DEVELOPMENT Environment...
>  ~
>  ~ FATAL: The gem merb-slices (= 0.9.9), [] was not found
>  ~
>  ~
>  ~ FATAL: The file merb-slices was not found
>  ~
>
> [EMAIL PROTECTED]:~/WebApps/appname/releases/20081025085933$ ls
> gems/gems/merb-slices-0.9.9/lib/
> generators  merb-slices  merb-slices.rb
> </code>
>
> Thanks,
> ~Michael
>
> On Mon, Oct 20, 2008 at 7:42 PM, fairchild <[EMAIL PROTECTED]>wrote:
>
>
>
> > My brain must be getting mushy.  I just needed to use
> > ./bin/merb
>
> > I coulda swore I tried that!  oh well.
>
> > I am still curious tho, how would I add a load_path?
> > ~Michael
>
> > On Oct 20, 6:51 pm, fairchild <[EMAIL PROTECTED]> wrote:
> > > I have spent way too much time trying to figure out how to do what I
> > > thought was the default behavior, loading required gems from Merb.root
> > > +/gems/gems/
> > > I can't seem to get the frozen gems to load, short of requiring them
> > > by full path.
>
> > > For instance:
>
> > > abbot([EMAIL PROTECTED]) :~/WebApps/lightsheet2
> > >  > ls gems/gems/httparty-0.1.3/lib/
> > > httparty/  httparty.rb
>
> > > abbot([EMAIL PROTECTED]) :~/WebApps/lightsheet2
> > >  > merb -i
> > > Warning: please use bin/merb to load merb-core-0.9.9 from ./gems
> > > Loading init file from /home/fairchild/WebApps/lightsheet2/config/
> > > init.rb
> > > Loading /home/fairchild/WebApps/lightsheet2/config/environments/
> > > development.rb
> > >  ~ Loaded DEVELOPMENT Environment...
> > >  ~
> > >  ~ FATAL: The gem httparty (>= 0), [] was not found
> > >  ~
> > >  ~
> > >  ~ FATAL: The file httparty was not found
>
> > > abbot([EMAIL PROTECTED]) :~/WebApps/lightsheet2
> > >  > cat config/dependencies.rb |grep http
> > > dependency 'httparty'
>
> > > I have tried putting
> > > puts $LOAD_PATH
> > > at the top of my dependencies.rb file just to check, and none of my
> > > frozen gem paths show up.  I must be missing something obvious?
>
> > > dependency 'httparty'
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"merb" 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/merb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to