Nathan Weizenbaum wrote: > Whenever Haml notices a discrepancy between the init.rb file stored in > the gem and the init.rb file installed in the Rails application, it > updates the installed file. This helps make sure that Haml is always > loaded properly. init.rb isn't changed very often, though (one change > was added prior to 2.0.0 and another, the comment in your patch below, > prior to 2.0.4) so the only explanation that I can come up with is that > you're occasionally loading different versions of the gem. I'd > reccommend making sure you only have the most recent version (2.0.6) > installed anywhere.
I've just done % find / -name *haml* And that has shown something. There are still files in /var/ruby/1.8/gem_home relating to haml, even though I have uninstalled the gem for haml from that ruby installation. I am removing all that rubbish and I'll see how it goes. Incidentally, there are some other haml gem installations but they are frozen and specific to other applications that are hosted on the same dev server. Could those unpacked gems be interfering even though they are inside another app's vendor/gems directory? Thanks Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" 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/haml?hl=en -~----------~----~----~----~------~----~------~--~---
