You can follow Radiant's lead and just expand them directly into vendor,
rather than vendor/gems. Radiant automatically adds those to the load path.
Sean
Vincent Pérès wrote:
Mohit Sindhwani wrote:
Vincent Pérès wrote:
end
But it doesn't work, the radiant gems like 'rubypants' can't be
loading... what is the best way to do that? Can you explain me?
I'm not sure about this, but I think you're supposed to freeze the
Radiant gem. It will take care of everything and put it under the
correct paths (I think vendor/radiant)
rake radiant:freeze:gems
Also, you can see if this helps:
Step 5 of: http://kb.mediatemple.net/questions/152/Installing+Radiant
Copy the radiant gem into your application, which will effectively
freeze the version of radiant you are using.
| cp -a ~/data/rubygems/gems/gems/radiant-0.6.6 vendor/radiant|
Cheers,
Mohit.
8/19/2008 | 4:18 PM.
Hello,
Thanks for your quick answer, but I'm 'unpacking' the radiant gem to use
it as a project.
'rake radiant:freeze:gems' don't do anything in my project.
In fact I would like to move the radiant gems dependencies in vendor/ to
vendor/gems/ and add my own gems.
Is there a way to do that or is it impossible?
Thanks a lot !
Vincent
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
