> > 2008/12/11 oleg dashevskii <[email protected]> > >> 1. Several days ago I tried to bundle RedCloth (4.1.1) into my app (merb >> 1.0.3). bin/merb refused to run until I also bundled echoe (which is a * >> development* dependency, as RedCloth gemspec states). echoe gem also >> pulled in rubyforge gem. > > > Were you running rubygems 1.2? This was a known bug that was resolved in > rubygems 1.3. >
No, it was 1.3.1. Hmm... strange. Seems I can't reproduce it. Ok then :) > > >> 2. There's no easy way to update bundled gems, no equivalent for `gem >> outdated` and `gem update`. > > > This will be resolved in 1.0.5. > > >> 3. All gems are saved in ./gems/cache, whereas only binary gems have >> really to (so that they could get redeployed). This adds more and more >> weight to repo. > > > Is this really a concern? Having all the gems in the cache means that you > don't have to rely on remote servers being up during deploy, but don't have > to store all the *files* in your repo in gems/gems. > Huh, I made my gems/gems into the repo and handcrafted a .gitignore which would prevent non-binary .gem's to sneak into git. What you suggest seems to be the opposite variant, perhaps saner. Wouldn't it be good to add gems/gems to .gitignore template for app? > >> 4. Looking into gems/gems, I cannot easily tell why a specific gem is >> there. Which gems depend on it? Maybe it should be uninstalled? > > > This will be resolved in 1.0.5 via thor merb:gems:audit. > > >> 5. Having to bundle rspec seems not sane (but otherwise bin/merb doesn't >> start). I'm not sure rspec is that helpful in the deployed app. > > > This will be resolved in 1.0.5 by allowing you to use your system repo, but > as a backup only (requires a monkey-patch to rubygems that will hopefully > make it into 1.4). > > Thanks for your feedback! Please keep it coming. > How cool. I'm very glad to hear that my gem pains gonna get relieved soon :) -- Oleg. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
