rc 0.3.0 → 0.3.1

data/.index

@@ -58,9 +58,11 @@ copyrights:
 created: '2011-11-06'
 summary: The best way to manage your application's configuration.
 title: RC
-version: 0.3.0
+version: 0.3.1
 name: rc
-description: ! 'R.C. is a multi-tenant configuration system for Ruby projects.
+description: ! 'R.C. is a multi-tenant runtime configuration system for Ruby projects.
 
-  R.C. can configure almost any Ruby tool or library.'
+  It can be used to configure almost any Ruby tool or library regardless
+
+  of whether that tool or library has dedicated support for RC or not.'
 date: '2013-01-08'

data/.rubyrc

@@ -73,8 +73,9 @@ end
 # Rake tasks 
 #
 config 'rake' do
+  task :default => [:test]
   desc 'run unit tests'
-  task 'test' do
+  task :test do
     puts "Rake Boo!"
   end
 end

data/HISTORY.md

@@ -1,5 +1,16 @@
 # RELEASE HISTORY
 
+## 0.3.1 / 2012-13-09
+
+This is bug fix release.
+
+Changes:
+
+* Fix rake tweak. Use `RC.configure` instead of `court`.
+* Fix #autoconfig? method's instance variable.
+* Fix #bootstrap_require to override correct hook.
+
+
 ## 0.3.0 / 2012-13-08
 
 This release is of the project finally begins to settle down the API.
@@ -30,7 +41,7 @@ Changes:
 * Overhaul and drastically simplify design.
 
 
-## 0.1.1 . 2012-04-09
+## 0.1.1 / 2012-04-09
 
 Initial release of RC. 
 

data/README.md

@@ -35,22 +35,21 @@ Then add `-rc` to your system's `RUBYOPT` environment variable.
     $ export RUBYOPT='-rc'
 
 You will want to add that to your `.bashrc`, `.profile` or equivalent configuration
-script, so it always available.
+script, so it is always available.
 
 
 ## Instruction
 
-To use RC in a project create a configuration file called either `.rc` or `RC.rb`. 
-Technically the file can be any variation of `rc` with an optional `.rb` extension,
-hidden or not and case-insensitive. Hidden file names have precedence if multiple
-matches exist. In this file add configuration blocks by name of the commandline tool.
+To use RC in a project create a configuration file called either `.ruby` or `.rubyrc`. 
+The longer name has precedence if both are present. In this file add configuration blocks
+by name of the commandline tool.
 
 For example, let's demonstrate how we could use this to configure Rake tasks.
-(Yes, Rake is not the most obvious choice, since most developers are just as happy
-to keep using a Rakefile. But a Rake example serves to show that it can be done,
-and also it makes a good tie-in with next example.)
+(Yes, Rake is not the most obvious choice, since developers are just as happy
+to keep using a Rakefile. But using Rake as an example serves to show that it
+*can* be done, and also it makes a good tie-in with next example.)
 
-    $ cat Config.rb
+    $ cat .rubyrc
     config :rake do
       desc 'generate yard docs'
       task :yard do
@@ -63,7 +62,7 @@ Now when `rake` is run the tasks defined in this configuration will be available
 You might wonder why anyone would do this. That's where the *multi-tenancy*
 comes into play. Let's add another configuration.
 
-    $ cat Config.rb
+    $ cat .rubyrc
     title = "MyApp"
 
     config :rake do
@@ -120,6 +119,13 @@ line option for specifying the profile.
 Beyond mere namespacing, some tools might utilize profiles for a more specific
 purpose fitting the tool. Consult the tool's documentation for details.
 
+Configurations can also be pulled in from other gems using the `from` option.
+
+    config :qed, :profile=>'simplecov', :from=>'qed'
+
+As long as a project includes its `.rubyrc` file (and any imported files)
+in it's gem package, it's possible to share configurations in this manner.
+
 
 ## Customization
 

data/lib/rc/interface.rb

@@ -243,7 +243,7 @@ module RC
     #
     #
     def autoconfig?
-      @autoconfigure
+      @autoconfig
     end
 
   protected
@@ -293,7 +293,7 @@ module RC
     # triggered on #require, not #load.
     #
     def bootstrap_require
-      def Kernel.required(feature)
+      def RC.required(feature)
         config = RC.configuration[feature]
         if config
           config.each do |config|

data/lib/rc/tweaks/rake.rb

@@ -1,6 +1,6 @@
 require 'rake'
 
-court 'rake' do |config|
+RC.configure 'rake' do |config|
   Module.new do
     extend Rake::DSL
     module_eval(&config)
@@ -8,7 +8,7 @@ court 'rake' do |config|
 end
 
 module Rake
-  RC_FILES = '.config.rb', 'config.rb', 'Config.rb'
+  RC_FILES = '.rubyrc', '.ruby'
 
   class Application
     remove_const(:DEFAULT_RAKEFILES)
@@ -28,4 +28,5 @@ module Rake
 end
 
 # Must manually configure tweaked libraries.
-RC.configure('rake')
+#RC.send(:configure_tool, 'rake')
+

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rc
 version: !ruby/object:Gem::Version
-  version: 0.3.0
+  version: 0.3.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-01-08 00:00:00.000000000 Z
+date: 2013-01-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: finder
@@ -91,9 +91,11 @@ dependencies:
     - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
-description: ! 'R.C. is a multi-tenant configuration system for Ruby projects.
+description: ! 'R.C. is a multi-tenant runtime configuration system for Ruby projects.
 
-  R.C. can configure almost any Ruby tool or library.'
+  It can be used to configure almost any Ruby tool or library regardless
+
+  of whether that tool or library has dedicated support for RC or not.'
 email:
 - transfire@gmail.com
 executables: []
@@ -164,3 +166,4 @@ signing_key:
 specification_version: 3
 summary: The best way to manage your application's configuration.
 test_files: []
+has_rdoc: