path: root/TODO
diff options
authorChris Larson <chris_larson@mentor.com>2010-06-24 11:01:25 -0700
committerChris Larson <chris_larson@mentor.com>2010-06-24 11:01:25 -0700
commitdc92299412afde3b978ca7adf76647763dfba6cc (patch)
tree1eb2694ec9e403690ab253c1ffbf5ac87056b739 /TODO
parentb781317b5006bc047a59e7fa3c93344115e78ccb (diff)
Add a couple long term, high impact TODO items
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Diffstat (limited to 'TODO')
1 files changed, 16 insertions, 0 deletions
diff --git a/TODO b/TODO
index b4211336..54ee646f 100644
--- a/TODO
+++ b/TODO
@@ -32,6 +32,22 @@
Looks like we may be able to use removeHandler.. will have to see how it
interacts with parent/child loggers.
+Long term, high impact:
+ - Change override application to actually *move* it over -- so the original
+ override specific version of the variable goes away, rather than sticking
+ around as a duplicate.
+ - Change the behavior when a variable is referenced and is unset. Today, it
+ evaluates to ${FOO} and then shell has a chance to expand it, but this is
+ far from ideal. We had considered evaluating it to the empty string, but
+ that has other potential problems. Frans Meulenbroeks has proposed just
+ erroring when this occurs, as we can always define default values for the
+ variables in bitbake.conf. This seems reasonable. My only concern with
+ that is the case where you want to reference a shell variable with odd
+ characters in it -- where you'd have to use ${} style shell variable
+ expansion rather than normal $. To handle that case, we'd really need a
+ way to escape / disable bitbake variable expansion, \${} perhaps.
- Leverage the python 2.6 multiprocessing module