rc 0.1.1 → 0.2.0

metadata

@@ -1,101 +1,49 @@
 --- !ruby/object:Gem::Specification
 name: rc
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.2.0
   prerelease: 
 platform: ruby
 authors:
+- Rubyworks
 - Trans
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-04-09 00:00:00.000000000 Z
+date: 2012-04-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: finder
-  requirement: &8666580 !ruby/object:Gem::Requirement
+  name: courtier
+  requirement: &20862920 !ruby/object:Gem::Requirement
     none: false
     requirements:
-    - - ! '>='
+    - - =
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 0.2.0
   type: :runtime
   prerelease: false
-  version_requirements: *8666580
+  version_requirements: *20862920
 - !ruby/object:Gem::Dependency
-  name: detroit
-  requirement: &8663120 !ruby/object:Gem::Requirement
+  name: courtier
+  requirement: &20862420 !ruby/object:Gem::Requirement
     none: false
     requirements:
-    - - ! '>='
+    - - =
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 0.2.0
   type: :development
   prerelease: false
-  version_requirements: *8663120
-- !ruby/object:Gem::Dependency
-  name: qed
-  requirement: &6999260 !ruby/object:Gem::Requirement
-    none: false
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: *6999260
-- !ruby/object:Gem::Dependency
-  name: ae
-  requirement: &6997500 !ruby/object:Gem::Requirement
-    none: false
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: *6997500
-description: ! "RC is a multi-tenant configuration system for Ruby projects.\nIt is
-  a spin-off of the original Confection project with\na simplifed overall design and
-  the ability to work with \nalmost any Ruby-based command line tool."
+  version_requirements: *20862420
+description: Courtier manages an application's configuration via a single multi-tenant
+  project file.
 email:
 - transfire@gmail.com
 executables: []
 extensions: []
-extra_rdoc_files:
-- LICENSE.txt
-- NOTES.md
-- HISTORY.md
-- README.md
-files:
-- .ruby
-- .yardopts
-- lib/c.rb
-- lib/rc/config.rb
-- lib/rc/configuration.rb
-- lib/rc/core_ext.rb
-- lib/rc/interface.rb
-- lib/rc/properties.rb
-- lib/rc/tool_configuration.rb
-- lib/rc/tweaks/rake.rb
-- lib/rc.rb
-- spec/00_concept.md
-- spec/01_config.md
-- spec/02_configuration.md
-- spec/03_import.md
-- spec/06_interface.md
-- spec/applique/ae.rb
-- spec/applique/file.rb
-- spec/applique/fixture/config.rb
-- spec/applique/fixture.rb
-- NOTES.md
-- LICENSE.txt
-- HISTORY.md
-- README.md
-- Config.rb
-homepage: http://rubyworks.github.com/rc
-licenses:
-- BSD-2-Clause
+extra_rdoc_files: []
+files: []
+homepage: http://github.com/rubyworks/courtier
+licenses: []
 post_install_message: 
 rdoc_options: []
 require_paths:
@@ -113,9 +61,10 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
+rubyforge_project: courtier
 rubygems_version: 1.8.11
 signing_key: 
 specification_version: 3
-summary: Multi-tenant configuration for Ruby.
+summary: The best way to manage your application's configuration.
 test_files: []
+has_rdoc: 

data/.ruby

@@ -1,51 +0,0 @@
----
-source:
-- var
-authors:
-- name: Trans
-  email: transfire@gmail.com
-copyrights:
-- holder: Rubyworks
-  year: '2011'
-  license: BSD-2-Clause
-requirements:
-- name: finder
-- name: detroit
-  groups:
-  - build
-  development: true
-- name: qed
-  groups:
-  - test
-  development: true
-- name: ae
-  groups:
-  - test
-  development: true
-dependencies: []
-alternatives: []
-conflicts: []
-repositories:
-- uri: git://github.com/rubyworks/rc.git
-  scm: git
-  name: upstream
-resources:
-  home: http://rubyworks.github.com/rc
-  docs: http://rubydoc.info/gems/rc/frames
-  code: http://github.com/rubyworks/rc
-  mail: http://groups.google.com/group/rubyworks-mailinglist
-  chat: http://chat.us.freenode.net/rubyworks
-extra: {}
-load_path:
-- lib
-name: rc
-title: RC
-revision: 0
-created: '2011-11-06'
-summary: Multi-tenant configuration for Ruby.
-version: 0.1.1
-description: ! "RC is a multi-tenant configuration system for Ruby projects.\nIt is
-  a spin-off of the original Confection project with\na simplifed overall design and
-  the ability to work with \nalmost any Ruby-based command line tool."
-organization: Rubyworks
-date: '2012-04-09'

data/.yardopts

@@ -1,8 +0,0 @@
---title "Runtime Configuration"
---readme README.rdoc
---protected
---private
-lib/**/*.rb
--
-[A-Z]*.*
-

data/Config.rb

@@ -1,68 +0,0 @@
-#!/usr/bin/env ruby
-
-#
-# Detroit assembly.
-#
-config :detroit do
-  service :email do |s|
-    s.mailto = ['ruby-talk@ruby-lang.org', 
-                'rubyworks-mailinglist@googlegroups.com']
-  end
-
-  service :gem do |s|
-    s.gemspec = 'pkg/rc.gemspec'
-  end
-
-  service :github do |s|
-    s.folder = 'web'
-  end
-
-  service :dnote do |s|
-    s.title  = 'Source Notes'
-    s.output = 'log/notes.html'
-  end
-
-  service :locat do |s|
-    s.output = 'log/locat.html'
-  end
-
-  service :vclog do |s|
-    s.output = ['log/history.html',
-                'log/changes.html']
-  end
-end
-
-#
-# QED test coverage report using SimpleCov.
-#
-# Use `$properties.coverage_folder` to set directory in which to store
-# coverage report this defaults to `log/coverage`.
-#
-config :qed, :cov do
-  require 'simplecov'
-
-  dir = $properties.coverage_folder
-
-  SimpleCov.start do
-    coverage_dir(dir || 'log/coverage')
-    #add_group "Label", "lib/qed/directory"
-  end
-end
-
-#
-# Rake tasks 
-#
-config :rake do
-  desc 'run unit tests'
-  task :test do
-    puts "boo"
-  end
-end
-
-#
-# Example configuration.
-#
-config :example do
-  puts "Configuration Example!"
-end
-

data/HISTORY.md

@@ -1,10 +0,0 @@
-# RELEASE HISTORY
-
-## 0.1.1 | 2012-04-09
-
-Initial release of RC. 
-
-Changes:
-
-* Happy first release.
-

data/LICENSE.txt

@@ -1,27 +0,0 @@
-Confection (http://rubyworks.github.com/confection)
-
-Copyright (c) 2011 Rubyworks. All rights reserved.
-
-License (spdx) BSD-2-Clause
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-
-   1. Redistributions of source code must retain the above copyright notice,
-      this list of conditions and the following disclaimer.
-
-   2. Redistributions in binary form must reproduce the above copyright
-      notice, this list of conditions and the following disclaimer in the
-      documentation and/or other materials provided with the distribution.
-
-THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
-INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
-AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
-NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR  SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
-EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-

data/NOTES.md

@@ -1,38 +0,0 @@
-# Developer Notes
-
-
-## 2012-04-07 | Toplevel DSLs
-
-If it were not for Ruby's mixing toplevel definitions into all
-objects, I likely would have used the simpler design of 
-just loading the config files directly (via `#load`).
-
-It's dissapointing that Ruby continues to insist on mixing toplevel
-methods into all objects. It would be much easier to write script
-DSLs if it did not, saving a good bit of code. In this case, for
-instance, I probably could have shaved off 20% to 40% of the 
-current code --neither the Config or the Configuration class
-would be needed, and the parser could be stripped down to just
-enough code to collect a list of profiles since that is all it
-would really be useful for then.
-
-
-## 2012-04-05 | Multiple Configurations
-
-Should multiple definitions for the same tool and profile be
-allowed?
-
-    config :qed, :cov do
-      ...
-    end
-
-    config :qed, :cov do
-      ...
-    end
-
-    configuration.invoke(:qed, :cov)
-
-Should both definitions be called, or just the later? I have decide
-that both will be called. If this becomes a concern, I may add a `#reconfig`
-method which would first clear the list of matching configurations.
-

data/README.md

@@ -1,182 +0,0 @@
-# RC - Runtime Configuration
-
-[Homepage](http://rubyworks.github.com/rc) /
-[Source Code](http://github.com/rubyworks/rc) /
-[Report Issue](http://github.com/rubyworks/rc/issues) /
-[Mailing List](http://googlegroups.com/group/rubyworks-mailinglist) /
-[IRC Channel](http://chat.us.freenode.net/rubyworks)
-
-[![Build Status](https://secure.travis-ci.org/rubyworks/rc.png)](http://travis-ci.org/rubyworks/rc)
-
-
-## Description
-
-RC, short for *Runtime Configuration*, is multi-tenant configuration system
-for Ruby tools. If was designed to facilitate Ruby-based configuration for
-multiple tools in a single file. It is extremely simple, and univerally applicable
-which makes it easy to understand and flexible in use.
-
-
-## Installation
-
-To use RC via tools that support RC directly, there is nothing you need to
-install. Installing the said tool should install `rc` via a dependency and
-load `rc` when the tool is used.
-
-To use RC with tools that don't provide direct support, first install RC
-in the usual manner via RubyGems.
-
-    $ gem install rc
-
-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.
-
-
-## Instruction
-
-To use RC in a project create a master configuration file for the project called
-`Config.rb`. The file can have any name that matches `.config.rb`, `Config.rb`
-or `config.rb`, in that order of precedence. 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.
-
-    $ cat Config.rb
-    config :rake do
-      desc 'generate yard docs'
-      task :yard do
-        sh 'yard'
-      end
-    end
-
-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
-    title = "MyApp"
-
-    config :rake do
-      desc 'generate yard docs'
-      task :yard do
-        sh "yard doc --title #{title}"
-      end
-    end
-
-    config :qedoc do |doc|
-      doc.title = "#{title} Demos"
-    end
-
-Now we have configuration for both the rake tool and the qedoc tool in
-a single file. Thus we gain the advantage of reducing the file count of our 
-project while pulling our tool configurations together into one place.
-Moreover, these configurations can potentially share settings as demonstrated
-here via the `title` local variable.
-
-RC also supports profiles, either via a `profile` block:
-
-    profile :cov
-      config :qed do
-        require 'simplecov'
-        ...
-      end
-    end
-
-Or via a second config argument:
-
-    config :qed, :cov do
-      require 'simplecov'
-      ...
-    end
-
-When utilizing the tool, set the profile via an environment variable.
-
-    $ profile='cov' qed
-
-Some tools that support RC out-of-the-box, may support a profile command
-line option for specifying the profile.
-
-    $ qed -p cov
-
-Still other tools might utilize profiles to a more specific purpose of
-the tool at hand. Consult the tool's documentation for details.
-
-
-## Qualifications
-
-RC can be used with any Ruby-based commandline tool that can be required by
-the same name as the tool, e.g. `rake` can be required via `require 'rake'`,
-and there exists some means of configuring the tool via a toplevel/global
-interface, or the tool has been customized to directly support RC.
-
-
-## Customization
-
-A tool can provide dedicated support for RC by loading the `rc/interface` script
-and defining a `run` procedure. For example, the `detroit` project defines:
-
-    require 'rc/interface'
-
-    RC.run('detroit') do |configs|
-      Detroit.rc_configs = configs
-    end
-
-When `detroit` gets around to loading a project's build assemblies, it will
-check this setting and evaluate the configs via Detroit's confgiruation DSL.
-
-Some tools may also need to run preconfiguration code before allowing RC to
-process configuration. Probably the most common use for this is to parse
-commandline arguments for a profile setting as an alternative to normal
-environment variable.
-
-    RC.run('qed') do
-      if i = ARGV.index('--profile') || ARGV.index('-p')
-        ENV['profile'] = ARGV[i+1]
-      end
-    end
-
-The `run` method forces the loading of `rc`, which triggers tool configuration,
-regardless of whether the end-user has set `RUBYOPT="-rc"`. If you wish for your
-tool to only work when `RUBYOPT` is set, then define `RC.processor` instead of
-`run`.
-
-
-## Dependencies
-
-### Libraries
-
-RC depends on the [Finder](http://rubyworks.github.com/finder) library
-to provide reliable load path and Gem searching. This is used when importing
-configurations from other projects.
-
-### Core Extensions
-
-RC uses two core extensions, `#to_h`, which applies to a few different
-classes, and `String#tabto`. These are *copied* from
-[Ruby Facets](http://rubyworks.github.com/facets) to ensure a high
-standard of interoperability.
-
-Both of these methods have been suggested for inclusion in Ruby proper.
-Please head over to Ruby Issue Tracker and add your support.
-
-* http://bugs.ruby-lang.org/issues/749
-* http://bugs.ruby-lang.org/issues/6056
-
-
-## Release Notes
-
-Please see HISTORY.rdoc file.
-
-
-## Copyrights
-
-Copyright (c) 2011 Rubyworks
-
-Confection is distributable in accordance with the **BSD-2-Clause** license.
-
-See LICENSE.txt file for details.
-