less todo
Signed-off-by: Steven Armstrong <steven@icarus.ethz.ch>
This commit is contained in:
		
					parent
					
						
							
								ce62775aec
							
						
					
				
			
			
				commit
				
					
						f671df1c67
					
				
			
		
					 1 changed files with 0 additions and 54 deletions
				
			
		| 
						 | 
				
			
			@ -1,57 +1,3 @@
 | 
			
		|||
x check: echo without parameters == valid in posix? bin/cdist-object-run:45 and others
 | 
			
		||||
x bin/cdist-object-run-all: "->" graphic: can be useful, but if -> consistent!
 | 
			
		||||
   -> all graphics could look cool:
 | 
			
		||||
 | 
			
		||||
   Object foo
 | 
			
		||||
   |
 | 
			
		||||
   |--> Requires ...
 | 
			
		||||
   |--> ...
 | 
			
		||||
 | 
			
		||||
   but maybe bad do parse from outside
 | 
			
		||||
 | 
			
		||||
x advantage of touch/rm loop vs. y == variable? bin/cdist-object-run-all
 | 
			
		||||
    also in bin/cdist-object-run
 | 
			
		||||
    -> cool :-)
 | 
			
		||||
x remove enormous amount of empty lines :-)
 | 
			
		||||
   - at end of file
 | 
			
		||||
   - between [ $# -eq 2 ] ||  and set
 | 
			
		||||
   - after if
 | 
			
		||||
   - before fi
 | 
			
		||||
 | 
			
		||||
x code aus cdist-object-run-all für requirements:
 | 
			
		||||
   in cdist-object-requirements oder so auslagern?
 | 
			
		||||
   cdist-object-run-all wäre dann eine schöne zwei-zeiler-schleife
 | 
			
		||||
 | 
			
		||||
x cdist-object-explorer-run and bin/cdist-object-run seem to contain
 | 
			
		||||
   very very similar code regarding transfer and co.
 | 
			
		||||
   -> indirect solved by moving code into cdist-object-explorer-run
 | 
			
		||||
 | 
			
		||||
x cdist-object-manifest-run: 
 | 
			
		||||
   # Tell cdist that there may be new objects -> WHO? :-)
 | 
			
		||||
 | 
			
		||||
x general: cdist-object-run-all looks like a good idea!
 | 
			
		||||
 | 
			
		||||
x cdist-type-explorer-push: wherefore if [ -d "$src_dir" ];?
 | 
			
		||||
   -> does this not even hide bugs?
 | 
			
		||||
   -> not sure whether covering cdist-dir in its own script makes
 | 
			
		||||
      sense, as cdist-dir push is only a one liner
 | 
			
		||||
      -> if cdist-dir does too less, enhance it
 | 
			
		||||
   => merge into cdist-object-explorer-run
 | 
			
		||||
 | 
			
		||||
x bin/cdist-object-run: type_explorer stuff: probably put into own binary
 | 
			
		||||
   - sounds like cdist-object-explorer-run is already the right executable to
 | 
			
		||||
      place such stuff into
 | 
			
		||||
 | 
			
		||||
x marker for type transferred / pushed goes into out/type/
 | 
			
		||||
   -> new variables for out/type
 | 
			
		||||
   -> new variables for out/type/.MARKERFOONAMEMEGOOD
 | 
			
		||||
 | 
			
		||||
x new function: __cdist_type_explorer_created $name
 | 
			
		||||
   if ! -d foo -> mkdir foo, echo $name >> foo/$NEW_FANCY_VAR
 | 
			
		||||
 | 
			
		||||
- export $__cdist_name_var_self=$__cdist_object_self -> non core
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
- align messages (already in todo for steven, but makes life much easier, thus repeated)
 | 
			
		||||
   -> prefix all object stuff with $__self
 | 
			
		||||
   -> __cdist_echo object string
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue