+log: should a type manifest be able to use type explorer values?
Signed-off-by: Steven Armstrong <steven@icarus.ethz.ch>
This commit is contained in:
parent
0c8432fd48
commit
1924e0cc63
1 changed files with 22 additions and 0 deletions
22
doc/dev/logs/2011-03-23.manifest_use_explorer
Normal file
22
doc/dev/logs/2011-03-23.manifest_use_explorer
Normal file
|
@ -0,0 +1,22 @@
|
|||
== Henne/Ei Problem ==
|
||||
manifest will explorer benutzen der noch gar nicht existiert,
|
||||
weil explorer ja auch object benutzen kann/soll/will welches erst von manifest
|
||||
erzuegt wird.
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
__foo/manifest
|
||||
|
||||
state_should="$(cat "$__object/parameter/state")"
|
||||
state_is="$(cat "$__object/explorer/state")"
|
||||
# BANG -> $__object/explorer/state does not exist at this point
|
||||
|
||||
if [ "$state_should" != "$state_is" ]; then
|
||||
__file /some/file --source /some/source
|
||||
fi
|
||||
|
||||
|
||||
|
||||
|
||||
|
Loading…
Reference in a new issue