summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJesse Koontz <jesselks@yahoo.com>2005-07-28 17:37:18 +0000
committerJesse Koontz <jesselks@yahoo.com>2005-07-28 17:37:18 +0000
commit54895daf480ae2f0e7d7e48c356feca9f2b0f691 (patch)
tree4dfb5f16eae40515e885061646f3edc69d8ce966
parent2d1e64373b2c9da2b89463c86fd95798c1c2e4ac (diff)
downloadpuppet-54895daf480ae2f0e7d7e48c356feca9f2b0f691.tar.gz
puppet-54895daf480ae2f0e7d7e48c356feca9f2b0f691.tar.xz
puppet-54895daf480ae2f0e7d7e48c356feca9f2b0f691.zip
Updated README, moved the old one to documentation/
git-svn-id: https://reductivelabs.com/svn/puppet/library/trunk@470 980ebf18-57e1-0310-9a29-db15c13687c0
-rw-r--r--Install0
-rw-r--r--README32
2 files changed, 0 insertions, 32 deletions
diff --git a/Install b/Install
deleted file mode 100644
index e69de29bb..000000000
--- a/Install
+++ /dev/null
diff --git a/README b/README
deleted file mode 100644
index 0731cdc0e..000000000
--- a/README
+++ /dev/null
@@ -1,32 +0,0 @@
-$Id$
-
-Introduction
-============
-There are currently three main components to Blink:
-
-Objects
--------
-These are the "primitives" of the language. If you want to affect the system,
-these are the only way to do it. Their base class is in blink/objects.rb, and
-they all inherit directly from that class.
-
-Attributes
-----------
-Each of the Objects are basically a collection of attributes. The attributes
-themselves are how the system is actually modified -- e.g., you set
-'file("/etc/passwd").owner = X', which modifies an attribute value, and that
-results in the system itelf being modified.
-
-Each attribute derives from blink/attribute.rb, but most attributes are actually
-defined in the same file as the class that uses them (e.g., blink/objects/file.rb).
-
-The Wrapper
------------
-At the top level is the Blink module. It doesn't do much right now
-
-Starting
-========
-You can start with bin/blinker, but it's probably better to just start in test/.
-I've been writing simple unit tests for most of the work I've done, so you can
-see how things do (and should) work by looking in there. Just run 'ruby
-<testfile>'.