THANKS! I mean... really THANKS!
I've merged the merb_datamapper stuff new version will be pushed ASAP. We want to have community gems such as merb_datamapper, merb_sequel, merb-auth, merb_cucumber to have independent version numbers. Reason for this is that we can release these gems in the independent releases which are more up to date to the 3rd parties. These gems should depend on merb ~> 1.1 which allows to match basically 1.x.x versions. And as for the rake install/build tasks I'm looking into it. Pavel On Jun 14, 7:14 pm, jonah honeyman <[email protected]> wrote: > I had some problems installing 1.2: > > * No longer able to install merb stack with `rake install` > * merb-auth is still versioned to 1.1 > * merb_datamapper.gemspec was missing a needed require statement > * merb stack gem had old dependency for data_mapper > > To get this going, I had to hack the rakefiles of all the stack gems, > bump merb-auth to 1.2, and make some changes to merb and merb_datamapper > gemspecs. > > Changes: > * merb -http://github.com/jonuts/merb/compare/master...fx-rake-install > * merb-auth > -http://github.com/jonuts/merb-auth/commit/ce3872e9d0d9f471ff9b272f8e5... > * merb_datamapper > -http://github.com/jonuts/merb_datamapper/compare/master...fx-rake-ins... > > Once I got everything working, I had no problems getting merb to boot. I > only needed to add Bundler.require to init.rb. > > In the bundle install upgrade, it bumped my haml version to the latest > release 3.0.12. This version DOES NOT WORK! I needed to dowgrade to the 2.0 > series to get Sass to compile my templates. I see there have been some > bug reports on the haml bug tracker, but all of them have been closed. > I'll take a look at this some more if I have the time, but 3.0.12 and > HEAD definitely do not work (unless there has been some changes to how > Sass is used that I am unaware of..) > > Other than that, things look fine. Good job! > > > > On Sun, Jun 13, 2010 at 01:40:00PM -0700, Pavel Kunc wrote: > > PLEASE TAKE A WHILE TO GET THROUGH THIS AND MAKE SURE THAT IF YOU'RE > > NOT HAPPY LET ME KNOW HERE OR ON THE IRC. > > > The release 1.2 is ready in the master and nobody did complain about > > this big change. > > > Please give positive or negative feedback. > > > Pavel > > > On May 26, 11:56�am, Pavel Kunc <[email protected]> wrote: > > > There has been many complaints about Bundler, requires and gem require > > > ordering issues. I know that Bundler does now or will support > > > requiring all the gems in the order specified in the Gemfile but still > > > there was an issue with Merb requiring bundler for it's work. > > > > I did some patches some time ago and I'm testing that on my apps to > > > remove this dependencies and implicit requiring of the gems using > > > Bundler.require. > > > > Current code is in the merb/master as 1.2. Please for more explanation > > > readhttp://wiki.github.com/merb/merb/release-120 > > > > So what I did and how it influence current apps? > > > > I've removed bundler dependency and bundler calls from the Bootladers. > > > This means > > > > a) You don't need to use Bundler with merb > > > b) At some point YOU need to require your gems > > > > Many people like to require gems in the runtime at the point when they > > > need the gem and not to require all gems during the booting. > > > > Basically what you need to do with your app on 1.2 is add either > > > Bundler.require (if bundler requires gems in correct order) to your > > > init.rb or add explicit requires (recommended) to init.rb or separate > > > file which is required in the init.rb. > > > > New generated applications now generate init with explicit requires. > > > > Feedback welcome! > > > > Pavel > > > -- > > 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 > > athttp://groups.google.com/group/merb?hl=en. -- 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.
