Jacques and Pavel,

I think backporting bundler support for 1.0.x makes no sense. The
primary features in 1.1 will be bundler, ruby 1.9 support,
active_model compliance and some bugfixes. There is nothing else
groundbreaking that would make an update more involved, so it seems to
me it's not worth taking the effort to backport the bundler stuff.
People should just switch to 1.1. Also, I wouldn't be surprised if
1.0.13 were the last release in the 1.0.x series.

cheers
snusnu

On Thu, Oct 1, 2009 at 04:16, Jacques Crocker <[email protected]> wrote:
>
> Hi Nick. Yeah, using the bundler will require Merb 1.1 (edge). Pavel
> and I were discussing backporting the changes to 1.0.x, but it
> probably makes more sense to focus on getting 1.1 done and released.
>
> On Sep 30, 2009, at 7:13 PM, Nicholas Orr wrote:
>
>>
>> My experience with merb 1.0.11 and bundler 0.6.0 = fail
>>
>> Things go awry inside bootstrap.rb looking for Gem::Version
>>
>> http://github.com/MagnitudeCMS/magnitudecms/tree/bundler
>>
>> Nick
>>
>> On Tue, Sep 29, 2009 at 10:13 AM, Jacques Crocker
>> <[email protected]> wrote:
>>> Thanks to the efforts of Pavel (github.com/pk), you can now use
>>> Merb with
>>> Carl & Yehuda's awesome new gem bundler (github.com/wycats/
>>> bundler). If
>>> you're working on a merb app, I would highly recommend trying this
>>> out and
>>> if it works ok, ditching the old thor tasks.
>>> These steps are a work in progress so let us know how it works out
>>> for you.
>>> I'll try and get some pages up on the Merb wiki soon that has a
>>> better step
>>> by step tutorial.
>>> First step, install bundler (latest 0.6.0)
>>> gem install bundler
>>> Install Merb 1.1 from Edge
>>> git clone git://github.com/wycats/merb.git
>>> cd merb
>>> gem install rspec extlib # required for merb's rake install
>>> New Project
>>> # generate new project using merb 1.1
>>> merb-gen app bookstore
>>> cd bookstore
>>> # create bundled app
>>> gem bundle
>>> # now you can run the bundled merb console
>>> bin/merb -i
>>> # you'll want to use bin/rake to use the app's rake tasks with the
>>> bundled
>>> gems
>>> bin/rake -T
>>> # you'll probably also want to install mongrel/thin to the bundle
>>> echo 'gem "mongrel"' >> Gemfile
>>> gem bundle
>>> # now you can run bin/merb to start the server
>>> bin/merb
>>> Migrate an Existing Project
>>> Pavel has pretty good instructions here:
>>> http://wiki.github.com/pk/merb/bundler
>>> cd existing_app
>>> # copy old dependencies to be the basis of the new Gemfile
>>> cp config/dependencies.rb ./Gemfile
>>> # tweak the Gemfile to the new format
>>> mate Gemfile
>>>     # add line: bundle_path "gems"
>>>     # add line: disabled_system_gems
>>>     # update merb version to 1.1
>>>     # find/replace "dependency" with "gem"
>>> # remove old junk
>>> rm config/dependencies.rb
>>> rm -Rf tasks/merb.thor
>>> # fix init.rb
>>> mate config/init.rb
>>>     # --remove line: require 'config/dependencies.rb'
>>> Using Bundler with Merb 1.0.12
>>> If you'd rather not upgrade to Merb 1.1 and still use the new
>>> bundler, let
>>> us know. Shouldn't be too difficult so I'll trying to come up with a
>>> solution for you.
>>>>
>>>
>>
>> >
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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