On Sun, Feb 22, 2009 at 3:34 PM, Grzegorz Junka <[email protected]> wrote:
> > David Nugent wrote: > > On 23/02/2009, at 8:04 AM, Grzesiu wrote: > > > >> Hi Conrad, > >> I am just starting my adventure with rails, so I am trying to start > >> with the most recent versions of ruby and rails to not have to upgrade > >> and struggle later, when it will be the time to deploy the app. > > > > > > My suggestion, taken from many years experience as a developer under > > FreeBSD: don't use bleeding edge versions when learning a new and > > unfamiliar infrastructure, and don't run bleeding edge versions when > > developing under a less popular and therefore lesser supported > > operating system such as FreeBSD. > > > > There are many caveats in using ruby 1.9 which contains a lot of > > fundamental and subtle changes to the ruby language without > > introducing an entire framework built originally for an earlier > > version. While bleeding edge / beta / candidate release versions of > > rails may cope with ruby 1.9, many if not most of the plugins you > > might be interested in playing with under rails will not be. And > > unless you want to reinvent many wheels, you WILL want to play with > > rails plugins. You want to learn the language and framework in a sane, > > well defined and tested environment, not in one that breaks easily. > > > > So, start from scratch. Uninstall all current versions of rails and > > ruby, go back to 1.8.6pl287 from ports and install the gems (including > > rails 2.2.2) also from FreeBSD ports and not via gem directly. This > > path avoids many of the problems you will otherwise hit, problems > > which have already been solved by the ports maintainers. Those > > problems are also easily solvable via google but it takes time, so > > best avoided unless you are a developer already very familiar with > > ruby, rails and FreeBSD and don't mind getting your hands dirty. Your > > life will be far more productive in the short term and you will hit > > few if any "strange errors". > > > > > > Happy developing, > > /d > > > Hi Conrad, > I understand the risk with bleeding edge versions, but in this case the > problem is with the first stable version of Ruby 1.9 series, not with > the edge versions. As I wrote, almost everything is working fine, > besides the not implemented fork in Ruby19 on FreeBSD. This looks > serious and may force me to downgrade to to ruby 1.8.6 and rails 2.2.2 > anyway. > > I was going to give it a go and see how many problems I will encounter > on the way. On the one side, solving these problems could help me > becoming familiar with Ruby/Rails. On the other side, if I could fix > some defects on Ruby 1.9 then I could contribute these fixes back to the > development branch. > > Lastly, even if I wanted I can't install rails from ports, because the > port got stuck at version 1.2.6. The only way of getting rails 2.2.2 on > FreeBSD is through gems. > > As a last thought, I think that I will try to install both versions at > once (ruby 1.8.6/rails 2.2.2 + ruby 1.9.1/rails edge). On FreeBSD these > rubies sit in different folders and it should be pretty easy to not mess > them together. Then I would be able to develop my code in older version > and from time to time try if it works in newer version, making some > fixes if necessary (i.e. using separated repositories and merging > changes in-between). That could work only if the 'fork' problem is > solvable. > > Anyway, many thanks for your help. > Regards > Greg > Hi Greg, I think that you're making something easy extremely complex. I had a working system using rails 2.3.0 RC1 and ruby 1.9.1 up in last than an hour. Next, you cannot create links the way that you're doing and expect things to work. Why? gem19 and gem18 refer to a different library path for their respective gem repository. Furthermore, ruby 1.9.1 comes with a version of rubygems to work with it. Also, ruby 1.9.1 and ruby 1.8.6 have their own versions of rake and rack locations. I mention both rake and rack here because they were required installs for rails 2.3.0 RC1 to install successfully. Now, if you are wanting to work with multiple ruby installations, I would recommend reading the following blog post: http://www.dcmanges.com/blog/install-multiple-versions-of-ruby-on-osx-leopard?disqus_reply=6142353#comment-6142353 Good luck, -Conrad > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
