| Age | Commit message (Collapse) | Author |
|---|
|
-Remove data_dict.py as it was not needed for sooo long
-Remove TODOs related to data_dict.py
-Remove data_dict from the MANIFEST
|
|
-Fix testcase by silenting the ververify error message
|
|
which reflect the execution of the respective tasks on providees
- add 'force' to toggle make.options.force
- switch to a more sane context sensitive completion method inspecting the 'usage' attribute
|
|
-Remove old code (python version >= 2.3 check)
-Remove commented code (as we've a scm)
-Fix most of the testcases (only one is failing)
-by importing string
-by removing new lines
-by changing '"' to "'"
-by reodering some elements
|
|
- save progress callback in function attribute
- remain completely silent when no progress callback is requested
|
|
- Introduce classes for commands and the command processor
- Autoregister available commands
- Fix 'shell' command to work with unlimited number of parameters
- Remove 'exec' command
|
|
- restore sys.stdout during raw_input, this repairs
tab completion which I broke two revisions ago
|
|
output
NOTE: Due to a limitation in the bbshell command processor, 'shell' and 'exec' are
currently broken when using more than one parameter. This will be sorted out asap.
|
|
all systems.
|
|
The BitBake shell now features a generic output buffer for the last 10 commands.
You can dump an overview about the buffered commands with 'buffers' and dump
the contents of a buffer with 'buffer <n>'. Likewise, 'pastebin <n>' uploads
the contents of the said buffer. NOTE: 'lasterror' is still available, but has been
renamed to 'lastlog'. The old pastebin command is still available with 'pastelog'.
|
|
|
|
- remove event property
- submit descriptive error messages when raising event exceptions
|
|
|
|
|
|
unify error messages
add new <directory> <bbfile> command
|
|
|
|
package)
- add fileRebuild (clean and rebuild a .bbfile)
|
|
- improve registerCommand
- build, clean, and rebuild no longer work on providees or bbfiles, but just on providees
- filebuild, fileclean and filerebuild work on bbfiles
- add which 'providee'
|
|
include 'time' into the scope. For bitbake 1.3.1 we need
to define which modules will be visible when executing
embedded python methods
|
|
- add expert mode - an embedded python interpreter
- add exec command
|
|
-Prepare the 1.3.0 release of bitbake
|
|
|
|
|
|
understood by any handler, rather than quietly returning None
|
|
- load command history on startup
- save command history on exit
Bug: A bug can be seen when you call rebuild on a package more than once -
somehow the make module no longer calls the tasks then.
|
|
|
|
|
|
|
|
Bump the version number to be different from the
last version
|
|
Pass more data to the parsing progressCallBack.
We will soon use this data to eliminate the long
delay before building.
bitbake/bin/bitbake:
Just change the signature of the callback method for now.
We will soon keep the 'parsing status' in a instance
we will fill while parsing and only evaluate in build_depgraph
|
|
-Do a deepcopy of the parent for the persistent
data storage constructor.
-Store the dict as _data member and not the instance
-Operate on the dict in the methods instead of the
DataSmart instances...
Happy deletion of the cache
|
|
-be less anoying and only print debug messages when
d is none
|
|
-Warn when init is called without a data instance, we're not able to reorder
them as it would break bitbake <= 1.2.1 and OpenEmbedded
bitbake/lib/bb/parse/BBHandler.py:
-Do not call fetch.init without a data instance. This changes the AtiCore
problem the OE folks are seeing a bit...
|
|
-Don't be too keen finding a bug in expand when there is None...
Fix the testcase to delete {TARGET_MOO} first.
|
|
-Write an expand test case that actually shows a bug I need to fix
|
|
-Add two test cases to the expand method. The behaviour
was not tested before.
|
|
-We've killed the default arguments in the methods
now the tests were updatet to initialize a data
instance to work again.
|
|
-Fix one bug in the unused data_dict.py. There is still one
left... again cookies for the one finding it
|
|
Return only the mtime from the os.stat syscall
bitbake/lib/bb/data_dict.py:
Return only the mtime from the os.stat syscall
|
|
Stop sf.net from bull?#*... us. We will fail when we wanted to
download a file and got something with a different name.
This should solve sf.net related problems as we go immediately to
the next mirror and it should work for all other packages as well.
|
|
Try to partially apply
http://wiki.python.org/moin/PythonSpeed/PerformanceTips?highlight=%28performance%29#dots avoid
finding data in bb
|
|
the bb module to obtain the version it uses.
|
|
Use the new data_smart dictionary
lib/bb/data_smart.py:
The old COW Implementation, made persistent and pass
the test suite.
I commit it because the persistent mode in data_dict.py seems
broken and I don't want to leave you with a broken bitbake.
Todo:
-do a deepcopy on the parent. When we pickle we use sharing
anyway and it is pretty obvious we will pickle as we're the
persistent implementation.
|
|
-Remove default arguments from the data methods. They
cast errors.
(we need to update the test case though)
lib/bb/parse/ConfHandler.py:
-Use the right dictionary
|
|
-Provide a special 'collection/dict' for the collected
bb-files. If we use a persistent storage (CACHE) we will
not hold any data instance in memory but load it from disk
on demand.
This reduces bitbakes memory usage to roughly 40MB. The initial
parsing currently takes roughly thirty seconds more.
lib/bb/make.py:
-Use the new data implementation for pkgdata.
-Do not access pkgdata[f] if we've the data already
in our hands
|
|
· -Add a method to get the modify time of named bb.data instance
· -Add a method to create a named bb.data instance. These instances
· inherit the global configuration.
lib/bb/data_dict.py:
· -Add persistents to the data_dict implementation, on the commit
method we will now pickle the internal dict
lib/bb/make.py:
-Use the new persistent/named bb.data methods.
|
|
Do not assume we hold a reference to the variable
we got with a bb.data.getVar*. Always set changes
back to the variable.
|
|
* Remove default params from the fetcher methods to avoid problems
with scoping. The meaning of 'd' is quite overloaded and we try
to undo it one by one. This change is a bit more invasive than
I had hoped for but it is needed.
-- Holger Hans Peter Freyther <freyther@handhelds.org>
|
|
-Move a createCopy method into data.py
-Make code creating deepcopies of the data instance
use this new createCopy
|
|
-bb.data is now a delegate to hookable Data implementation.
-bb.data.init() is the 'factory' method to create a instance
of a concrete implementation.
-Kill assumptions that bb.data.init() returns a {} (python dict)
-Add the old Dictionary Based Implementation as data_dict.py
|
Holger Hans Peter Freyther
Michael 'Mickey' Lauer
Phil Blundell
Chris Larson