Age | Commit message (Collapse) | Author |
|
Add a function to bring the command environment in sync with the data
dictonary.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
|
|
the empty_environment() function to clear the environment
|
|
Poky)
|
|
|
|
2008-10-07 Julian Chu <Julian_Chu@openmoko.com>
Reviewed by Holger.
The packagekit git repository contains a symlink and on fetching the
pruning failed as "packagekit" is not a directory but a symlink to a
directory.
* lib/bb/utils.py:
|
|
|
|
now only pass certain whitelisted variables into the data store. If BB_PRESERVE_ENV is set bitbake will use all variable from the environment. If BB_ENV_WHITELIST is set, that whitelist will be used instead of the internal bitbake one. Alternatively, BB_ENV_EXTRAWHITE can be used to extend the internal whitelist.
|
|
function
|
|
(via Poky)
|
|
|
|
|
|
poky). utils.py: Fix a spelling mistake.
|
|
functions in the fetcher code
|
|
(closes #2027)
|
|
|
|
BitBake trunk is now GPLv2 only, no mix of
MIT,FreeBSD License is left.
Update GPL headers to point to the correct
address of the FSF
Update the list of authors. Uli Luckas,
Seb Frankengul and Tim Amsell contributed to
the sourcecode as well
|
|
|
|
bitbake/lib/bb/build.py:
bitbake/lib/bb/utils.py:
bitbake/lib/bb/shell.py:
bitbake/lib/bb/providers.py:
bitbake/lib/bb/msg.py:
bitbake/bin/bitbake:
bitbake/bin/bitdoc:
bitbake/classes/base.bbclass:
Start an overhaul of the message handling in bitbake:
- Introduce a new msg module to replace the existing simple calls.
- The msg module adds the conncept of message domains so ultimately we can
select which kinds of debug messages we want to see (it uses an Enum class
for this)
- Add a warn logging level for things the user should really pay attention to
as note is a little overloaded at present
- Start converting to use the new fuctions
|
|
Do not report RuntimeErrors for SkipPackage and FuncFailed
|
|
Kill the code duplication
|
|
Do not go past the buffer
(this looks like copy and paste)
|
|
Do not report Skipped Packages as runtime
error
|
|
-Be less verbose
|
|
-This not Thiis
-Print the RuntimeError with context gosh
that is looking awesome.
-Now debugging errors in custom bbclasses,
python methods should be much more easy
|
|
Create a work in progress version for
better_execute. With advanced error reporting
facilities.
bitbake/lib/bb/build.py:
Use better_execute
bitbake/parse/parse_py/BBHandler.py:
Use better_execute instead of exex
|
|
We compile strings into code. In case of erros the traceback
is not useful at all. It doesn't print the function name,
accurate line number etc.
Introduce a better_compile method that excepts the Error
and prints the surrounding lines of code.
We make use of it on the parsing level and execution level
of python methods.
|
|
- Fix a RDEPENDS parsing bug in utils:explode_deps()
(versions containing spaces didn't parse correctly)
bitbake/lib/bb/fetch/git.py:
- Update git fetcher behaviour to match git changes
|
|
-add explode_deps method to return
a list of package names from a string (RDEPENDS)
Patch courtsey Richard Purdie (rpurdie@openedhand.com)
bitbake/bin/bitbake:
-major overhaul on dependency tracking and improvement
to the previous commit.
Build Runtime Depends and Runtime Recommendations at the
same time as the package is built.
Patch courtsey Richard Purdie (rpurdie@openedhand.com)
|
|
Said make module has been factorered out back in the old days when we had two concurrent
oemake implementations which were in need of code sharing. Nowadays, there's no
more use of a seperated make module and in fact the split has always been a bit
artificial.
A brief overview of the changes:
* create utils.py which contains three unbound functions for comparing versions
* create a class BBConfiguration that holds variables which were formerly living in make module scope
* make functions use the BBConfiguration instance that lives in BBCooker instance
* move functions into the BBCooker class, adapt them to work as class methods
* integrate the function of the bbread executable into BitBake; use it with option '-e' and (optionally) -b
* remove make.py
* remove bbread
* adapt the shell module which has been using the make module directly
|