--todo, begin cleanup of cdist-language.text

Signed-off-by: Nico Schottelius <nico@kr.ethz.ch>
This commit is contained in:
Nico Schottelius 2011-02-26 11:08:07 +01:00
parent b2def229fd
commit be7b68815a
4 changed files with 4 additions and 6 deletions

View File

@ -39,6 +39,7 @@ but is not. Or: The reason why I began to write cdist.
* No surprise factor
* Consistency in behaviour, naming and documentation
* Easy integration nacked installations
* Simple and well-known DSL: posix shell
## Requirements

View File

@ -1,6 +1,6 @@
Steps needed until 1.0:
- finish type __file
x finish type __file
- finish type __package
- cleanup documentation (see below)
@ -81,5 +81,6 @@ x execute code on client (stage 5)
- DOC document that $type/manifest is executed for every object/instance
- DOC: types can always access __cdist_out_objects, __cdist_out_explorers, __cdist_out_execs
--> create cdist-variables document?
- cleanup READMEs
- include generation in makefile

View File

@ -0,0 +1 @@
Prepare documentation for 1.0.0.

View File

@ -40,11 +40,6 @@ The three stages are used to seperate configurations:
- "manifests" (use the same name here?) will be run/sourced
- inheritance possible via sourcing
- cdist-lib always preloaded
- library == functions?
- matching on explored items, not only on host name?
- match function in host? [optional]
- explorer ran before!
- document exported variables!
use __ prefix instead of __cdist (shorter writing, __ is defined as sytem anyway)