Changes between Version 20 and Version 21 of FeatureRequests

Timestamp:

Oct 3, 2006, 12:49:21 PM (18 years ago)

Author:

garonne

Comment:

--

FeatureRequests

@@ -39 +39 @@
 This would require that Foo declared the Foo_native_version macro to  
 be set to 1.2.3 (in this example).
+
+
+=== ''CMT team's answer'' ===
+
+This implies to overide the macro Foo_native_version within the glue package. Useful probably for testing external package in a fast way. See ticket #35.
 
 == 3. Wildcard or prioritized project dependency support (DavidQ) ==
@@ -128 +133 @@
 will still have the existing symlink structure.
 
+=== ''CMT team's answer'' ===
+
+It is clearly a specific Atlas item which should be resolved within Atlas_policy, Atlas fragments/pattern and well documented for future use. 
+
+
 == 6. Revisit g77 include path (DavidQ) ==
 
@@ -136 +146 @@
 should revisit this, perhaps in conjunction with 7. below.
 
+=== ''CMT team's answer'' ===
+
+No comment.
+
+
 == 7. Investigate whether we can use gfortran instead of g77(DavidQ) ==
 
@@ -143 +158 @@
 uniformity. We would need to ensure that gfortran was shipped with  
 the kit, but that's done already.
+
+=== ''CMT team's answer'' ===
+
+No comment.
 
 == 8. cmt co tag (DavidR) ==
@@ -193 +212 @@
 We are thinking of having a snapshot functionality to get an `image' of a configuration. Ideally this snapshot would be in xml and could be translated (via XSLT) in other format (Xcode, Visualx.x, and so on): see ticket #32.
 
+Another point is to convert requirements file into xml by a tool.
 
 == 12. Separate the 'build' environment from the 'user' environment (SébastienB) ==
@@ -202 +222 @@
 confusion (while developers are trying to reproduce users' bugs) and ease 
 spotting mis-configuration.
+
+=== ''CMT team's answer'' ===
+
+see 11 ?
 
 == 13. Introduce a mechanism to describe runtime dependencies between packages (SébastienB) ==
@@ -218 +242 @@
   * Runtime dependencies
   * Etc.
+ * Identify the common parts
 
 Probably for the version 2 ;)
@@ -267 +292 @@
 === ''CMT team's answer'' ===
 
-Compilation seems to be clearly a place for improvements. See ticket #34
+Compilation seems to be clearly a place for improvements but we are rewriting our own patched make version. 
+Hace we reached the Make limit, e.g. as it only deals with timestamps ? See ticket #34.
 
 == 15. Profile and optimise CMT (SébastienB) ==
@@ -293 +319 @@
 === ''CMT team's answer'' ===
 
-See ticket #34
+See also ticket #34.
 
 == 16. have a build-dir location which can be configured (SébastienB) ==
@@ -316 +342 @@
 precompiled-header plug-in.
 
+=== ''CMT team's answer'' ===
+
+
+
+
 == 18. produce makefiles structured according to the "Recursive Make Considered Harmful" prescription (AndreiG) ==
 
@@ -367 +398 @@
 === CMT team's answer ===
 
-Interesting links. Should take time to well understand it/make tries. See ticket #34.
+Interesting links. Should take time to well understand it/make tries. The logic exists for describing the graph(cmt show uses)
+, we can imagine to generate a global makefile. See also ticket #34.
 
 == 19. Avoid creating archive libraries unless explicitly requested (DavidQ) ==