You mean it leaves traces even after you do "gem clean" ? On Mon, Dec 29, 2008 at 3:02 AM, Matt Harrison <[email protected] > wrote:
> > Matt Harrison wrote: > > 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. > > Well clearing out the files from old gems that weren't removed when the > gem was uninstalled seems to have done the trick :) > > I will have to remember in future that uninstalling a gem does not > remove all traces, but at least it appears I've got that annoyance > silenced. > > Thanks for the hints > > 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 -~----------~----~----~----~------~----~------~--~---
