ergo 0.3.0

data/.index

@@ -0,0 +1,62 @@
+---
+revision: 2013
+type: ruby
+sources:
+- var
+authors:
+- name: Trans
+  email: transfire@gmail.com
+organizations:
+- name: Rubyworks
+requirements:
+- name: notify
+- groups:
+  - build
+  development: true
+  name: detroit
+- groups:
+  - build
+  development: true
+  name: mast
+- groups:
+  - test
+  development: true
+  name: qed
+- groups:
+  - test
+  development: true
+  name: ae
+conflicts: []
+alternatives: []
+resources:
+- type: home
+  uri: http://rubyworks.github.com/ergo
+  label: Homepage
+- type: code
+  uri: http://github.com/rubyworks/ergo
+  label: Source Code
+- type: bugs
+  uri: http://github.com/rubyworks/ergo/issues
+  label: Issue Tracker
+repositories:
+- name: upstream
+  scm: git
+  uri: git://github.com/rubyworks/ergo.git
+categories: []
+copyrights:
+- holder: Rubyworks
+  year: '2010'
+  license: BSD-2-Clause
+customs: []
+paths:
+  lib:
+  - lib
+created: '2010-07-05'
+summary: The best build tool, logically!
+title: Ergo
+version: 0.3.0
+name: ergo
+description: ! 'Ergo is an automated build tool with a slick set-logic based
+
+  state/rules system, perfect for performing continuous integration.'
+date: '2013-02-16'

data/.yardopts

@@ -0,0 +1,10 @@
+--title Fire
+--readme README.md
+--plugin tomdoc
+--private
+--protected
+lib
+-
+*.md
+*.txt
+

data/HISTORY.md

@@ -0,0 +1,47 @@
+# RELEASE HISTORY
+
+## 0.3.0 / 2013-02-13
+
+Major release removes tasks. There are only rules now! In
+addition *books* have been added which allow rules to be
+grouped together. Oh! And you might have noticed the name
+of the project has changed from *Fire* to *Ergo*.
+
+Changes:
+
+* Deprecate tasks.
+* Add rule books.
+* Rename project to Ergo.
+
+
+## 0.2.0 / 2013-02-12
+
+This is the last version with tasks. Tasks are being deprecated
+for two reasons: a) they add a great deal of complexity to the
+syntax and the implementation via their need for dependencies;
+and b) tasks have proven to be an excuse for poorly designed 
+rules, which, if properly written, would do the job just as well
+if not better than any task. So it was decided that if tasks are
+needed, then they should be provided via dedicated task system,
+not via the rules system.
+
+Changes:
+
+* Default rule file is now `.fire/rules.rb` or `rules.rb`.
+* Rules can depend on tasks using same hash notation as tasks.
+* Modified the `#rule` method to define file rules given a string.
+* Deprecated the `file` method for defining file rules.
+
+
+## 0.1.0 / 2012-04-10
+
+This is the initial release of Fire. Fire is state and rules-based
+continuous integration and build tool.
+
+Special thanks to Ari Brown for letting us take over the fire gem
+for this project. "Fire" is perfect fit.
+
+Changes:
+
+* Happy first release day!
+

data/LICENSE.txt

@@ -0,0 +1,25 @@
+(BSD-2-Clause License)
+
+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/README.md

@@ -0,0 +1,161 @@
+# Ergo 由
+
+[Homepage](http://rubyworks.github.com/ergo) /
+[Report Issue](http://github.com/rubyworks/ergo/issues) /
+[Source Code](http://github.com/rubyworks/ergo) /
+[IRC Channel](http://chat.us.freenode.net/rubyworks)
+
+***"Logic programming meets the build tool."***
+
+Ergo is a build tool that promotes continuous integration via logic
+programming. With Ergo, the Ruby developer defines rules and state
+conditions. The rules are applied when their state conditions are
+met. Through repetitive application, this allows a project to all
+but manage itself.
+
+Ergo is not complicated. It goes not require a bazillion plug-ins.
+Although some external tools can be helpful and used with it, and
+it makes some procedures more convenient --for example it makes
+FileUtils methods directly available in the build script context,
+mostly it just trusts the developer to know how to write the build
+scripts they need.
+
+Below you will find a brief "Hot Minute" guide for getting up and
+running with Ergo quickly. It's just enough to give you familiarity
+the basic ideas of Ergo and how to start putting it to good use.
+For more detailed instruction, explanation of terms and how the
+dickens does it work under-the-hood, please consider any of the
+following resources.
+
+* [Overview of Ergo](https://github.com/rubyworks/ergo/wiki/Overview-of-Ergo)
+* [Helpful FAQs](https://github.com/rubyworks/ergo/wiki/FAQ)
+* [Ergo Recepies](https://github.com/rubyworks/ergo/wiki/Ergo-Recipes)
+* [API Documentation](http://rubydoc.info/gems/ergo/frames)
+
+
+## Ergo in a Hot Minute
+
+To install, either use RubyGems directly:
+
+```
+  $ gem install ergo
+```
+
+Or add `gem "ergo"` to your Gemfile and run:
+
+```
+  $ bundle install
+```
+
+Create a `.ergo` directory in your project.
+
+```
+  $ mkdir .ergo
+```
+
+Edit the `.ergo/script.rb` file.
+
+```
+  $ vi .ergo/script.rb
+```
+
+And add the following example script to the file.
+
+```ruby
+  manifest = %w[bin/**/* lib/**/* *.md]
+
+  state :need_manifest? do
+    if File.exist?('MANIFEST')
+      files = manifest.map{ |d| Dir[d] }.flatten
+      saved = File.readlines('MANIFEST').map{ |f| f.strip }
+      files != saved
+    else
+      true
+    end
+  end
+
+  desc "update manifest"
+  rule need_manifest? do
+    files = manifest.map{ |d| Dir[d] }.flatten
+    File.open('MANIFEST', 'w'){ |f| f << files.join("\n") }
+  end
+
+  desc "run my minitests"
+  rule 'lib/**/*.rb' do |libs|
+    $: << 'lib'
+    files = Dir.glob('test/**/*_test.rb') 
+    files.each{|file| require "./" + file}
+  end
+```
+
+Now run it with:
+
+    $ ergo
+
+And there you go. Ergo, in a hot minute!
+
+
+## A Few More Minutes
+
+As the capable Ruby programmer, it probable doesn't require much explanation
+to understand the above code and what happened when you ran it. Just the
+same it can help to go over it with the proper terminology. Of course,
+the rules in our example are simplistic and they make some basic
+assumptions about a project, so you will want to modify these to suite your
+needs (or dispose of them and write fresh). Nonetheless, this example
+provides some clear examples of the basics of writing Ergo scripts.
+
+In the example we first create a *state* called `update_manifest?`. It
+simply checks to see if the list of files in the project's MANIFEST
+file matches the project files expected to be there. Notice it returns
+a boolean value, true or false. Along with this state we create a *rule*
+that uses the state by calling the `update_manifest?` method. This method
+was created by the state definition above. The *rule procedure* updates the 
+MANIFEST file whenever the state return `true`, i.e. the manifest does
+not have the expected content.
+
+At the end of our example script we create an additional rule. This
+one does not reference a defined state. Instead it create a *file state*
+implicitly by passing a string argument to `rule`. A file state has a
+very simple and very useful definition. It returns `true` whenever a
+matching file has changed from one execution of `ergo` to the next.
+In other words, per this example, whenever a Ruby file in the `lib` 
+directory changes, Ergo is going to run the units tests in the `test` 
+directory.
+
+Okay, so now we have a example rules script and have a basic grasp of
+how it works. And we know we can run the rules simple by invoking the
+`ergo` command on command line. But if we want to have ergo run
+automatically periodically, we can pass it the number of seconds to
+wait between runs via the `-a/--auto` option.
+
+    $ ergo -a 180
+
+See it pays to read all the way to the end ;)
+
+
+## Contributing
+
+The Ergo [repository](http://github.com/rubyworks/ergo) is hosted on GitHub.
+If you would like to contribute to the project (and we would be over joyed
+if you did!) the rules of engagements are very simple.
+
+1. Fork the repo.
+2. Branch the repo.
+3. Code and test.
+4. Push the branch.
+4. Submit pull request.
+
+
+## Copyrights
+
+Ergo is copyrighted open-source software.
+
+  Copyright (c) 2011 Rubyworks. All rights reserved.
+
+It is modifiable and redistributable under the terms of the
+[BSD-2-Clause](http::/spdx.org/licenses/BSD-2-Clause) license.
+
+See the enclosed LICENSE.txt file for details.
+
+(火)

data/bin/ergo

@@ -0,0 +1,4 @@
+#!/usr/bin/env ruby
+require 'ergo'
+Ergo::CLI.fire!
+

data/demo/03_runner/01_applying_rules.md

@@ -0,0 +1,51 @@
+## Applying Rules
+
+The `Runner` class handles running rules. It takes `System` as an argument and
+can run all applicable rules or a specific book of rules.
+
+### True/False Rules
+
+The simplist rule state is `true`, which means it will always run, or
+`false` which means it will never run. These states are not very useful,
+but they should still work.
+
+Given a @system defined with a simple always-true rule, and another
+always-false rule:
+
+    rule true do
+      assert true
+    end
+
+    rule false do
+      assert false
+    end
+
+Then the Runner should run the true rule and not the false rule when
+applying the system's rules.
+
+    runner = Ergo::Runner.new(:system=>@system, :root=>Dir.pwd)
+
+    runner.run
+
+### Simple State Rule
+
+Given a @system defined with a simple state:
+
+    state :simple do
+      true
+    end
+
+    rule simple do
+      assert true
+    end
+
+    rule false do
+      assert false
+    end
+
+Then the Runner should run the simple rule, but not the other.
+
+    runner = Ergo::Runner.new(:system=>@system)
+
+    runner.run
+

data/demo/applique/ae.rb

@@ -0,0 +1 @@
+require 'ae'

data/demo/applique/ergo.rb

@@ -0,0 +1,7 @@
+require 'ergo'
+
+When 'iven a @system defined' do |text|
+  @system = Ergo::System.new
+  @system.module_eval(text)
+end
+

data/lib/ergo.rb

@@ -0,0 +1,20 @@
+# ruby standard library
+require 'fileutils'
+require 'digest/sha1'
+require 'ostruct'
+
+# third party library
+require 'notify'
+
+# internal library
+require_relative 'ergo/core_ext'
+require_relative 'ergo/match'
+require_relative 'ergo/shellutils'
+require_relative 'ergo/state'
+require_relative 'ergo/rule'
+require_relative 'ergo/ignore'
+require_relative 'ergo/digest'
+require_relative 'ergo/book'
+require_relative 'ergo/system'
+require_relative 'ergo/runner'
+require_relative 'ergo/cli'

data/lib/ergo.yml

@@ -0,0 +1,62 @@
+---
+revision: 2013
+type: ruby
+sources:
+- var
+authors:
+- name: Trans
+  email: transfire@gmail.com
+organizations:
+- name: Rubyworks
+requirements:
+- name: notify
+- groups:
+  - build
+  development: true
+  name: detroit
+- groups:
+  - build
+  development: true
+  name: mast
+- groups:
+  - test
+  development: true
+  name: qed
+- groups:
+  - test
+  development: true
+  name: ae
+conflicts: []
+alternatives: []
+resources:
+- type: home
+  uri: http://rubyworks.github.com/ergo
+  label: Homepage
+- type: code
+  uri: http://github.com/rubyworks/ergo
+  label: Source Code
+- type: bugs
+  uri: http://github.com/rubyworks/ergo/issues
+  label: Issue Tracker
+repositories:
+- name: upstream
+  scm: git
+  uri: git://github.com/rubyworks/ergo.git
+categories: []
+copyrights:
+- holder: Rubyworks
+  year: '2010'
+  license: BSD-2-Clause
+customs: []
+paths:
+  lib:
+  - lib
+created: '2010-07-05'
+summary: The best build tool, logically!
+title: Ergo
+version: 0.3.0
+name: ergo
+description: ! 'Ergo is an automated build tool with a slick set-logic based
+
+  state/rules system, perfect for performing continuous integration.'
+date: '2013-02-16'