| 
									
										
										
										
											2011-03-29 10:38:35 +02:00
										 |  |  | 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! | 
					
						
							| 
									
										
										
										
											2011-03-28 18:09:02 +02:00
										 |  |  |    -> all graphics could look cool: | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |    Object foo | 
					
						
							|  |  |  |    | | 
					
						
							|  |  |  |    |--> Requires ... | 
					
						
							|  |  |  |    |--> ... | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |    but maybe bad do parse from outside | 
					
						
							| 
									
										
										
										
											2011-03-28 18:16:55 +02:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2011-03-29 10:38:35 +02:00
										 |  |  | 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 :-) | 
					
						
							| 
									
										
										
										
											2011-03-28 18:31:26 +02:00
										 |  |  |    - at end of file | 
					
						
							|  |  |  |    - between [ $# -eq 2 ] ||  and set | 
					
						
							|  |  |  |    - after if | 
					
						
							|  |  |  |    - before fi | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2011-03-29 10:38:35 +02:00
										 |  |  | x code aus cdist-object-run-all für requirements: | 
					
						
							| 
									
										
										
										
											2011-03-28 18:31:26 +02:00
										 |  |  |    in cdist-object-requirements oder so auslagern? | 
					
						
							|  |  |  |    cdist-object-run-all wäre dann eine schöne zwei-zeiler-schleife | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2011-03-29 10:38:35 +02:00
										 |  |  | x cdist-object-explorer-run and bin/cdist-object-run seem to contain | 
					
						
							| 
									
										
										
										
											2011-03-28 18:31:26 +02:00
										 |  |  |    very very similar code regarding transfer and co. | 
					
						
							| 
									
										
										
										
											2011-03-29 10:38:35 +02:00
										 |  |  |    -> indirect solved by moving code into cdist-object-explorer-run | 
					
						
							| 
									
										
										
										
											2011-03-28 18:31:26 +02:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2011-03-29 10:38:35 +02:00
										 |  |  | x cdist-object-manifest-run:  | 
					
						
							| 
									
										
										
										
											2011-03-28 18:38:08 +02:00
										 |  |  |    # Tell cdist that there may be new objects -> WHO? :-) | 
					
						
							| 
									
										
										
										
											2011-03-28 18:31:26 +02:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2011-03-29 10:38:35 +02:00
										 |  |  | x general: cdist-object-run-all looks like a good idea! | 
					
						
							| 
									
										
										
										
											2011-03-28 18:31:26 +02:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2011-03-29 10:38:35 +02:00
										 |  |  | - export $__cdist_name_var_self=$__cdist_object_self -> non core | 
					
						
							| 
									
										
										
										
											2011-03-28 18:31:26 +02:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2011-03-29 10:38:35 +02:00
										 |  |  | - 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 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | - 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 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | - marker for type transferred / pushed goes into out/type/ | 
					
						
							|  |  |  |    -> new variables for out/type | 
					
						
							|  |  |  |    -> new variables for out/type/.MARKERFOONAMEMEGOOD | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | - new function: __cdist_type_explorer_created $name | 
					
						
							|  |  |  |    if ! -d foo -> mkdir foo, echo $name >> foo/$NEW_FANCY_VAR | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | - align messages (already in todo for steven, but makes life much easier, thus repeated) | 
					
						
							|  |  |  |    -> prefix all object stuff with $__self | 
					
						
							|  |  |  |    -> __cdist_echo object string | 
					
						
							|  |  |  |       -> $__cdist_object_self :-) |