This project is archived and is in readonly mode.
non-gem packages 2.1.x contain hardcoded MacOS ruby script paths and out-of-date configuration
When downloading Rails from RubyForge using the zip or tgz distributions, the scripts in the "public/" and "script/" directories have a shebang line with hardcoded MacOS system paths. In addition, the config/database.yml file still has MySQL as the default database, instead of the current default of sqlite3.
The non-gem distributions should contain the same files as would be generated by the gem after running "rails" with no arguments.
The second problem of database config is a simple patch to "railties/Rakefile" (attached). The first problem is due to the use of "copy_with_rewritten_ruby_path" in this same file; I'm not sure I understand why this is used at all, since it's almost certain to be wrong (on my machine, it results in /usr/bin/ruby1.8). I'm hoping one of the devs can weigh in and say whether it's ok to remove this method.
-
Repository(from [f8f22dac8e08656f1798d6bf2aa8accc534b077d]) Update non-gems distributions to use sqlite3 as the default, matching the "rails" command default [#1270 non-gem packages 2.1.x contain hardcoded MacOS ruby script paths and out-of-d... status:committed]
Signed-off-by: David Heinemeier Hansson david@loudthinking.com http://github.com/rails/rails/co...
-
DHH- State changed from new to committed
-
Christopher Currie
This next patch modifies the Rakefile so that the BIN_FILES scripts don't have their shebang lines changed. I've not updated the dispatch.* files, because the "rails" command does appear to modify them, so I need to understand why, and if it's no longer necessary, change "rails" and the Rakefile.