In commit fd5c6e2c97c1d71823a42ffbdece14c8913c58b3, Jeremy Kemper updated the bundled i18n from 0.3.3 to 0.3.7. In the process, he also removed the suffixed /lib from the path to load it from. I just removed my system copies of i18n to use the newer bundled version 0.4.1 but now it''s complaining with "LoadError: no such file to load -- i18n". Indeed, there is no i18n.rb file in the parent directory so was this change a mistake? If I add /lib to the path again, it works. I would file a bug but I''m surprised no one else has commented on this so maybe I''m missing something here? Regards, James -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Hi, I actually the one who did the 0.3.7 -> 0.4.1 commit. Actually, I think I made a mistake in that commit. Thank you for pointing it out. I will provide a patch soon. - Prem On 29 มิ.ย. 2553, at 18:29, James Le Cuirot wrote:> In commit fd5c6e2c97c1d71823a42ffbdece14c8913c58b3, Jeremy Kemper > updated the bundled i18n from 0.3.3 to 0.3.7. In the process, he also > removed the suffixed /lib from the path to load it from. I just > removed my system copies of i18n to use the newer bundled version > 0.4.1 but now it''s complaining with "LoadError: no such file to load > -- i18n". Indeed, there is no i18n.rb file in the parent directory so > was this change a mistake? If I add /lib to the path again, it works. > I would file a bug but I''m surprised no one else has commented on this > so maybe I''m missing something here? > > Regards, > James > > -- > You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. > To post to this group, send email to rubyonrails-core@googlegroups.com. > To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
On Jun 29, 1:19 pm, Prem Sichanugrist <sikand...@gmail.com> wrote:> I will provide a patch soon.That did the trick, thanks. :) -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
No problem, and sorry for submitting the bad patch ;) Sent from my iPad On 29 มิ.ย. 2010, at 23:14, James Le Cuirot <chewi@aura-online.co.uk> wrote:> On Jun 29, 1:19 pm, Prem Sichanugrist <sikand...@gmail.com> wrote: >> I will provide a patch soon. > > That did the trick, thanks. :) > > -- > You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. > To post to this group, send email to rubyonrails-core@googlegroups.com. > To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.