I currently have several non public gems in my project installed using the 1.0.6 thor task. Here's how I bundled them:
- install the gems from .gem file to my system gems - add to dependencies.rb - run thor merb:gem:install The thor task checks system gems first so it'll install it from there. >From then on, it'll be in the cache, so after you check it in, it'll be available via redeploy for others. Probably not an ideal scenario so I think the bug is still valid. But this technique should serve as a workaround. On Dec 18, 1:34 am, Carl Lerche <[email protected]> wrote: > I believe that non public gems are a known issue. I just added a > ticket in lighthouse to be sure. > > http://merb.lighthouseapp.com/projects/7433/tickets/1139-should-be-ab... > > -carl > > On Dec 18, 1:21 am, Geoff Smith <[email protected]> wrote: > > > Great work! > > > Do you have any advice on how to bundle non-public gems using this > > setup? > > > On Dec 17, 8:26 pm, Wayne Seguin <[email protected]> wrote: > > > >http://www.jingproject.com/ > > > > On Dec 17, 2008, at 15:23 , Carl Lerche wrote: > > > > > Hey guys, > > > > > I recorded a screencast last night with Yehuda demonstrating the new > > > > features in Merb 1.0.5 (aka, the new bundler release). I believe most > > > > of the pains people have been having are now solved, so check it out. > > > > >http://splendificent.com/2008/12/merb-dependencies-and-bundler-conque... > > > > > later, > > > > -carl --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
