1 Changes in BitBake 1.3.?:
2 - Create a new Fetcher module to ease the
3 development of new Fetchers.
4 Issue #438 fixed by rpurdie@openedhand.com
5 - Make the Subversion fetcher honor the SRC Date
7 Issue #555 fixed by chris@openedhand.com
8 - Expand PREFERRED_PROVIDER properly
9 Issue #436 fixed by rprudie@openedhand.com
10 - Typo fix for Issue #531 Philipp Zabel for the
12 - Introduce a new special variable SRCDATE as
13 a generic naming to take over CVSDATE.
14 - Introduce a new keyword 'required' In contrast
15 to include parsing will fail if a to be included
18 Changes in BitBake 1.3.2:
19 - reintegration of make.py into BitBake
20 - bbread is gone, use bitbake -e
21 - lots of shell updates and bugfixes
22 - Introduction of the .= and =. operator
23 - Sort variables, keys and groups in bitdoc
24 - Fix regression in the handling of BBCOLLECTIONS
25 - Update the bitbake usermanual
27 Changes in BitBake 1.3.0:
28 - add bitbake interactive shell (bitbake -i)
29 - refactor bitbake utility in OO style
30 - kill default arguments in methods in the bb.data module
31 - kill default arguments in methods in the bb.fetch module
32 - the http/https/ftp fetcher will fail if the to be
33 downloaded file was not found in DL_DIR (this is needed
34 to avoid unpacking the sourceforge mirror page)
35 - Switch to a cow like data instance for persistent and non
36 persisting mode (called data_smart.py)
37 - Changed the callback of bb.make.collect_bbfiles to carry
39 - Drastically reduced the amount of needed RAM by not holding
40 each data instance in memory when using a cache/persistent
43 Changes in BitBake 1.2.1:
44 The 1.2.1 release is meant as a intermediate release to lay the
45 ground for more radical changes. The most notable changes are:
47 - Do not hardcode {}, use bb.data.init() instead if you want to
48 get a instance of a data class
49 - bb.data.init() is a factory and the old bb.data methods are delegates
50 - Do not use deepcopy use bb.data.createCopy() instead.
51 - Removed default arguments in bb.fetch