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 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.
Hi Conrad,
May I ask on which system you've got rails 2.3.0 RC1 and ruby 1.9.1
installed within an hour? I guess it was MacOS X?
I am not sure if what you write applies to FreeBSD. As I wrote I
haven't installed any gems for Ruby18, so all execs such as rake, gem
etc refer only to ruby19. Moreover, on FreeBSD all files relevant to
Ruby18 and Ruby19 are being installed in different folders, for
example:
system files:
/usr/local/lib/ruby/1.9
/usr/local/lib/ruby/1.8
local files (nothing is installed for ruby18 in local repositories):
/root/.gem/ruby/1.9 (under this folder are bin, cache, doc, gems,
specifications)
/home/grzesiu/.gem/ruby/1.9 (the same here)
I can run both version of ruby independently i.e. using irb18 and
irb19 (irb was a copy of irb18). When I install rails, depending on
which version of ruby I am using, it is being installed either to the
folder within 1.8 or 1.9, and depending on whether I am using root or
a normal user account, either system or local repositories are used. I
don't know how is it on other systems but apparently the ruby port on
FreeBSD was designed such that you can install both versions of ruby
at the same time (there are some system libraries which depend
specifically on ruby 1.8.6, so using ruby 1.9.1 would be impossible if
it was not done). Even when I installed Passenger it automatically
detected that and asked to add this line to httpd.conf:
PassengerRuby /usr/local/bin/ruby19
In my opinion the problem I am having has nothing to do with how I am
installing Rails. The unimplemented fork in Ruby 1.9.1 port on FreeBSD
suggests problems in the port itself, and that the problem wouldn't
disappear if I installed the port differently. The problem is
reproducible when I am using irb19 only, without even touching rails
or gems.
I wonder what happens when you type this command in irb on your Mac OS
X:
@pid = fork
I've just checked it in irb18 and it works, which is clearly a proof
of problems with the irb19 version only.
Regards
Greg
I'm only tracking edge because I need features that are only in ruby
1.9.1 in my rails app. It probably won't be too long before 1.9.* and
2.3.* is stable, so I would recommend what the others did - play around
with the stable stuff first. Edge has it's own issues. You can upgrade
later when these new versions are stable.
--
Posted via http://www.ruby-forum.com/.
Nearly one year later, I'm having the same problem!
Best Regards, dieinzige
--
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 rubyonra...@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.