diff options
author | Chris Larson <chris_larson@mentor.com> | 2010-06-10 10:35:31 -0700 |
---|---|---|
committer | Chris Larson <chris_larson@mentor.com> | 2010-09-03 18:51:54 -0700 |
commit | 3b2c1fe5ca56daebb24073a9dd45723d3efd2a8d (patch) | |
tree | 1f77ebed5e5f48fd786286a51dd697113cb7ea28 /TODO | |
parent | c23c015cf8af1868faf293b19b80a5faf7e736a5 (diff) | |
download | bitbake-3b2c1fe5ca56daebb24073a9dd45723d3efd2a8d.tar.gz |
Switch bitbake internals to use logging directly rather than bb.msg
We use a custom Logger subclass for our loggers
This logger provides:
- 'debug' method which accepts a debug level
- 'plain' method which bypasses log formatting
- 'verbose' method which is more detail than info, but less than debug
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 17 |
1 files changed, 9 insertions, 8 deletions
@@ -15,14 +15,15 @@ exception like that, *perhaps*, to abstract away exceptions raised by event handlers, but it has no place in bb.build.exec_task -- Leverage the python logging module - -- Convert bb modules to stop using the bb.msg functions. -- Switch the messaging wrappers in the bb package to use the logging module - directly, as we'll be deprecating the bb.msg versions, but these should - stay around for the metadata to use. -- Deprecate the bb.msg functions. -- Should we use the logging module rather than print in the knotty ui? +- BUG: if you chmod 000 local.conf, it silently doesn't parse it, when it + should really fail, so the user can fix the problem. + +- Audit bb.fatal usage - these should all be able to be replaced with + exceptions +- Add deprecation warnings to the bb.msg functions +- Figure out how to handle the ncurses UI. Should some of our logging + formatting stuff be made common to all of bitbake, or perhaps all UIs via + the UIHelper? Long term, high impact: |