Changes between Version 6 and Version 7 of TDAQ

Timestamp:

May 17, 2013, 11:27:42 AM (11 years ago)

Author:

/C=FR/O=CNRS/OU=UMR8607/CN=Antoine Perus/emailAddress=perus@…

Comment:

--

TDAQ

@@ -52 +52 @@
 Somme immediate comments on requirements of tdaq (made with Antoine & Sébastien)
 
-* Indeed packages are either
-** simple packages with mainly libraries & applications
-** of non standard Policy packages
+Indeed packages are either:
 
-Simple packages should be converted into Yaml easily
+  1. simple packages with mainly libraries & applications
+  1. of non standard Policy packages
 
-Policy packages require manual construction of hwaf "functions"
-
-* remains the question of "tags"
-** what is the replacement concept? ("variant"?)
-** there are "automatic" variants (deduced from the platform/hardware/... introspection)how to express the 
-** and non automatic variants (eg with or without graphic)
-** how to implement in hwaf
-** how to express in yaml (or more generally in declarative language)
-** how to express the different forms of macro/set values?
-
-* questions:
-** how to express the Yaml form of path/path_append/path_prepend/path_remove
-
+=== Comments: ===
+  * Simple packages should be converted into Yaml easily
+  * Policy packages require manual construction of hwaf "functions"
+  * Remains the question of "tags"
+    * what is the replacement concept? ("variant"?)
+    * there are "automatic" variants (deduced from the platform/hardware/... introspection) - how to express them 
+    * and non automatic variants (eg with or without graphic)
+    * how to implement in hwaf
+    * how to express in yaml (or more generally in declarative language)
+    * how to express the different forms of macro/set values?
+    
+  * Questions:
+    * how to express the Yaml form of path/path_append/path_prepend/path_remove