Is there a simple way to bootstrap merb directly from the Subversion repository, rather than first installing it as a gem? I can do the following if I already have an old gem lying around: merb -g testapp # using an old gem cd testapp rake merb:freeze_from_svn Unfortunately, that means I''m using an old version of the generator. So for example, when I just tried this, the generator made a conf/ directory, whereas the code in trunk expects config/. Equally, I can''t test any new features recently added into the generator (such as the snazzy new screens committed in r464-r466), without first building trunk into a gem, and gem installing it over my existing one. I have tried: svn co http://svn.devjavu.com/merb/trunk merb cd merb ruby -Ilib bin/merb -g /var/tmp/test123 but I get: Couldn''t find ''merb'' generator /usr/lib/ruby/gems/1.8/gems/rubigen-1.0.3/lib/rubigen/lookup.rb:159:in `lookup'' /usr/lib/ruby/gems/1.8/gems/rubigen-1.0.3/lib/rubigen/lookup.rb:164:in `instance'' /usr/lib/ruby/gems/1.8/gems/rubigen-1.0.3/lib/rubigen/scripts/../scripts.rb:30:in `run'' /v/build/merb-trunk/lib/merb/generators/merb_app/merb_app.rb:13:in `run'' ./lib/merb/server.rb:216:in `run'' bin/merb:6 Cheers, Brian.
The way I''ve seen it done is to run "rake install" in a checked out version of merb. Then it just installs a new gem over top of whatever gem your system has. Duane On Aug 31, 2007, at 2:51 PM, Brian Candler wrote:> Is there a simple way to bootstrap merb directly from the Subversion > repository, rather than first installing it as a gem? > > I can do the following if I already have an old gem lying around: > > merb -g testapp # using an old gem > cd testapp > rake merb:freeze_from_svn > > Unfortunately, that means I''m using an old version of the > generator. So for > example, when I just tried this, the generator made a conf/ directory, > whereas the code in trunk expects config/. > > Equally, I can''t test any new features recently added into the > generator > (such as the snazzy new screens committed in r464-r466), without first > building trunk into a gem, and gem installing it over my existing one. > > I have tried: > > svn co http://svn.devjavu.com/merb/trunk merb > cd merb > ruby -Ilib bin/merb -g /var/tmp/test123 > > but I get: > > Couldn''t find ''merb'' generator > /usr/lib/ruby/gems/1.8/gems/rubigen-1.0.3/lib/rubigen/lookup.rb: > 159:in `lookup'' > /usr/lib/ruby/gems/1.8/gems/rubigen-1.0.3/lib/rubigen/lookup.rb: > 164:in `instance'' > /usr/lib/ruby/gems/1.8/gems/rubigen-1.0.3/lib/rubigen/scripts/../ > scripts.rb:30:in `run'' > /v/build/merb-trunk/lib/merb/generators/merb_app/merb_app.rb: > 13:in `run'' > ./lib/merb/server.rb:216:in `run'' > bin/merb:6 > > Cheers, > > Brian. > _______________________________________________ > Merb-devel mailing list > Merb-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/merb-devel
On Fri, Aug 31, 2007 at 04:47:16PM -0600, Duane Johnson wrote:> The way I''ve seen it done is to run "rake install" in a checked out > version of merb. Then it just installs a new gem over top of > whatever gem your system has.Sure - but it takes a while for it to rebuild ri and rdoc etc. I was just checking to see if I''d missed a trick. If not, I''ll stick with this way. Thanks, Brian.
I do this: rake gem; sudo gem install pkg/merb-0.4.0.gem --no-ri --no-rdoc -- Duane (Sorry, Brian for that previously unexplained shortcut command, gemi) On Sep 1, 2007, at 5:46 AM, Brian Candler wrote:> On Fri, Aug 31, 2007 at 04:47:16PM -0600, Duane Johnson wrote: >> The way I''ve seen it done is to run "rake install" in a checked out >> version of merb. Then it just installs a new gem over top of >> whatever gem your system has. > > Sure - but it takes a while for it to rebuild ri and rdoc etc. > > I was just checking to see if I''d missed a trick. If not, I''ll > stick with > this way. > > Thanks, > > Brian.