Hmm, I don't have an issue compiling sass :/ In my gem file I have gem "haml", "2.2.0" gem "merb-haml", merb_gems_version
gem "chriseppstein-compass", "0.8.16", :require_as => "compass" I also use Compass so maybe the combo of all three have everything work?? In my project I also wanted sass compiled from string input as well as files on the filesystem and made additions that I load in init.rb http://github.com/MagnitudeCMS/magnitudecms/blob/master/config/init.rb#L35 Maybe you are leaving something out as to what you are doing... (I'm using Merb 1.1 with bunlder for above) Nick On Wed, Oct 14, 2009 at 4:49 AM, Tony Mann <[email protected]> wrote: > Supposedly in Merb 1.0.12 you do not need a specify a dependency on Sass as > long as you have a dependency on merb-haml. However, this is not correct. If > you don't explcitly require sass.rb, you will get the error: > > NameError: uninitialized constant Sass::VERSION > > > when Sass tries to compile your stylesheets. > > The problem is that merb-haml.rb requires "sass/plugin", when it should > require "sass". Sass::VERSION is defined in sass.rb. > > I was about to file this as a ticket in Lighthouse when I saw this closed > ticket<https://merb.lighthouseapp.com/projects/7433/tickets/1073-sass-doesnt-work-out-of-the-box-needs-require-sass> > which > describes the same problem. Should I reopen this ticket or file a new one? > > The workaround for now is to explicitly require Sass. The right fix is to > change merb-haml to require sass and not sass/plugin. > > ..tony.. > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
