TemplateRunner adds gems to environment file in reverse of written order

Each successive gem command in an app template places the corresponding config.gem line above the previous one.

This makes the environment file's config.gem lines the reverse order of the app templates gem commands, potentially causing requirement failures.

Example app template gem commands:

gem 'authlogic'
gem 'authlogic-oid', :lib => "authlogic_openid"
gem 'somegem'

Creates these environment.rb lines:

config.gem 'somegem'
config.gem 'authlogic-oid', :lib => 'authlogic_openid'
config.gem 'authlogic'

Running the rake gems task then would abort at that authlogic-oid line with:

rake aborted!
undefined method add_acts_as_authentic_module' for ActiveRecord::Base:Class</code>
</pre>



I can't think of an easy fix other than some sort of counter to keep track of how many lines have been added after the sentinel.



For now I'll just have to construct my templates in reverse order as needed.