1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
rails--rails/activesupport
2006-12-24 14:53:35 +00:00
..
lib Update load once paths to prevent nested once constants from being detected and claimed by an external non-once load. References #6720 2006-12-24 14:53:35 +00:00
test Checkin failing test case related to load once paths 2006-12-24 14:41:29 +00:00
CHANGELOG Update load once paths to prevent nested once constants from being detected and claimed by an external non-once load. References #6720 2006-12-24 14:53:35 +00:00
install.rb Added install.rbs for all frameworks and made all of them generic enough not to require maintenance #1013, #1012 2005-04-02 07:29:08 +00:00
MIT-LICENSE Version updates and missing licenses 2006-09-15 10:13:27 +00:00
Rakefile Eliminate Active Support warnings. 2006-08-29 08:24:04 +00:00
README Fix READMEs (closes #2680) [coffee2code] 2005-11-07 09:51:47 +00:00

= Active Support -- Utility classes and standard library extensions from Rails

Active Support is a collection of various utility classes and standard library extensions that were found useful
for Rails. All these additions have hence been collected in this bundle as way to gather all that sugar that makes
Ruby sweeter.


== Download

The latest version of Active Support can be found at

* http://rubyforge.org/project/showfiles.php?group_id=182

Documentation can be found at 

* http://as.rubyonrails.com


== Installation

The preferred method of installing Active Support is through its GEM file. You'll need to have
RubyGems[http://rubygems.rubyforge.org/wiki/wiki.pl] installed for that, though. If you have it,
then use:

  % [sudo] gem install activesupport-1.0.0.gem


== License

Active Support is released under the MIT license.


== Support

The Active Support homepage is http://www.rubyonrails.com. You can find the Active Support
RubyForge page at http://rubyforge.org/projects/activesupport. And as Jim from Rake says:

   Feel free to submit commits or feature requests.  If you send a patch,
   remember to update the corresponding unit tests.  If fact, I prefer
   new feature to be submitted in the form of new unit tests.

For other information, feel free to ask on the ruby-talk mailing list
(which is mirrored to comp.lang.ruby) or contact mailto:david@loudthinking.com.