require_gem 'rails', '= 1.1.0'doesn't work so good. Really the Typo team dropped the ball on this one, it isn't like they didn't know that Rails 1.1 was coming or that they were going to have problems. I am disappointed with the response from them which has been near silence.
Even when they are ready the memory consumption/CPU usage now exceeds the max per process on Textdrive. So without some clean up to the codebase people will be in for a shock when they can get to Rails 1.1 and Typo 4.0 on a shred host because it will get killed anyway. *sigh*
On 3/29/06, Pascal Belloncle <[EMAIL PROTECTED]
> wrote:
Sean Mountcastle <smountcastle <at> gmail.com> writes:
>
> > Try running:
> >
> > rake freeze_edge REVISION=3303
> >
> > On your Typo install directory. This is the equivalent to the Rails 1.0gem .
>
> Thanks Steve, that works. But the whole purpose of RubyGems is so
> that you could have multiple versions of gems installed and have your
> Ruby app require a specific version -- does this not work with Rails
> at all?
>
> Sean
>
To lock your "require" to a specific version you can follow the instructions from
http://wiki.rubyonrails.com/rails/pages/HowtoLockToSpecificRailsVersions
Maybe the environment.rb from typo should use this?
Thanks,
Pascal.
_______________________________________________
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list
_______________________________________________ Typo-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/typo-list
