summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* bitbake: cooker/cookerdata: Fix up event handling for hobRichard Purdie2013-05-241-1/+2
| | | | | | | | | The init function call was clobbering data hob relies on injecting, fix this so the data injected by hob isn't overwritten. (Bitbake rev: 64ca1aa1fd5f0473196b6cd805637fa644a92173) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: build: Avoid empty promisesRichard Purdie2013-05-241-1/+1
| | | | | | | | | | | | The "see xxx for further information" is misleading since it is just the same information. Clarify just to mention the that this is the location of the logfile without any empty promise. [YOCTO #4343] (Bitbake rev: 7088c0e8553dd3c408b5bc06f8c34d5b72e9ea9a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-layers: fix show-appends and flatten for recent cooker changesPaul Eggleton2013-05-241-8/+8
| | | | | | | | | | | | | Fixes the show-appends and flatten subcommands for recent refactoring in cooker. [YOCTO #4536] [YOCTO #4535] (Bitbake rev: 54817d0de667941ee68fe3490684159e2d90e9c5) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker/cookerdata: Improve configuration object handlingRichard Purdie2013-05-244-16/+16
| | | | | | | | | | | | | | | | | | | | | Originally it seemed like a good idea to keep the parameters around. Having seen this in real life use, its incorrect, we should pull all the data we need into the cooker's configuguration and then use this to build the datastore. Being able to just build the datastore from the parameters seemed like a good idea but having a dummy cooker configuration object is now looking like the better option. This also fixes failures in hob since the parseFiles command can call into cooker directly now and reset the configuration prefiles and postfiles at will, rather than the indirect calls before which were breaking the datastore (e.g. BBPATH wasn't set). The cleanup this allows in tinfoil illustrates how this change makes more sense. (Bitbake rev: f50df5b891bf318f12fc61c74adfcc626cc6f836) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2: Fix missing assignmentRichard Purdie2013-05-241-1/+1
| | | | | | | | The assignment to True was missing from the code, well spotted Saul! (Bitbake rev: e493fe8cb4953935f01361ffc0240e5818ebb283) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker/cookerdata/event: Improve class handlers managementRichard Purdie2013-05-243-3/+13
| | | | | | | | | Similarly to the execution context changes, establish better lifetime management API of the class event handlers. (Bitbake rev: 54e35a6cceead9521f8b1dacd48e55064e85c8bd) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker/cookerdata/utils: Improve context managementRichard Purdie2013-05-243-10/+22
| | | | | | | | | | | | | | | The current execution context management for bitbake is ugly and the use of a global variable is nasty. Fixing that is hard, however we can improve things to start to establish an API for accessing and changing that context. This patch also adds in an explicit reset of the context when we reparse the configuration data which starts to improve the lifecycle of the data in setups like hob. (Bitbake rev: 6c3281a140125337fc75783973485e16785d05a1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: event: Drop Handled/NotHandled status return valuesRichard Purdie2013-05-241-11/+0
| | | | | | | | These have long since been deprecated, lets remove them. (Bitbake rev: 3dc83bbb1bf387bb7ecea2e17f0f72cfccecba92) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker.py: Remove global scope class event handlersRichard Purdie2013-05-241-0/+2
| | | | | | | | | | | | | | | | Its confusing when an event handler in for example a bbclass receives events for a recipe which doesn't use the class. This is due to the class event handlers having confusing scope. Worse, the issue is not deterministic and the events a handler will see depends on the parse order. To avoid these issues, remove the class event handler global scope and only have class handlers recieve events for recipes using the class. (Bitbake rev: 7fb95f3d133e440d463d2faa7151c731f8e1ae96) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: methodpool: Retire it, remove global method scopeRichard Purdie2013-05-244-51/+5
| | | | | | | | | | | | | | | | | Having a global method scope confuses users and with the introduction of parallel parsing, its not even possible to correctly detect conflicting functions. Rather than try and fix that, its simpler to retire the global method scope and restrict functions to those locations they're defined within. This is more what users actually expect too. If we remove the global function scope, the need for methodpool is reduced to the point we may as well retire it. There is some small loss of caching of parsed functions but timing measurements so the impact to be neglibile in the overall parsing time. (Bitbake rev: 4d50690489ee8dc329a9b0c7bc4ceb29b71e95e9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: methodpool: Conflicting methodnames should be a fatal errorRichard Purdie2013-05-241-1/+1
| | | | | | | | | | When this error occurs, the build should stop, not continue uninterrupted. [YOCTO #4460] (Bitbake rev: acd6d7ffa8813b3b11cad9145e8e614a695ae04a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity.bbclass: Drop dubious printRichard Purdie2013-05-241-1/+0
| | | | | | (From OE-Core rev: be4cd4614a2a702130d18e9d082fd83a15faa013) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildhistory: Sync with bitbake changesRichard Purdie2013-05-231-1/+4
| | | | | | | | | | Adjust to the recent changes in the git fetcher. This code should work with current and previous versions of bitbake and can be cleaned up when we move to new bitbake versions. (From OE-Core rev: 835b64d4e9ed7b627b56a75d529f1a403c5db1a8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm-postinsts.bb: enable postinst loggingChen Qi2013-05-231-8/+9
| | | | | | | | | | | | | | | | Enable postinst logging by checking the configuration in ${sysconfdir} /default/postinst. In this way, the postinst logging is enabled if 'debug-tweaks' is in IMAGE_FEATURES, and at the same time, we avoid unnecessary rebuild if IMAGE_FEATURES is changed. [YOCTO #4262] (From OE-Core rev: 6f2aa32f10c24c84e581128bb3a976ef071197ac) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* opkg: modify the run-postinst script to enable postinst loggingChen Qi2013-05-231-1/+6
| | | | | | | | | | | | | | | | Enable postinst logging by checking the configuration in ${sysconfdir} /default/postinst. In this way, the postinst logging is enabled if 'debug-tweaks' is in IMAGE_FEATURES, and at the same time, we avoid unnecessary rebuilt if IMAGE_FEATURES is changed. [YOCTO #4262] (From OE-Core rev: 35be6ffc19a5156aa029397707f1e6869684b821) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dpkg: modify the run-postinst script to enable postinst loggingChen Qi2013-05-231-5/+6
| | | | | | | | | | | | | | | | Enable postinst logging by checking the configuration in ${sysconfdir} /default/postinst. In this way, the postinst logging is enabled if 'debug-tweaks' is in IMAGE_FEATURES, and at the same time, we avoid unnecessary rebuilt if IMAGE_FEATURES is changed. [YOCTO #4262] (From OE-Core rev: 881880992ac0edc5f928f7e3d2a8f3f993284df6) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image.bbclass: add postinst_enable_loggingChen Qi2013-05-231-0/+11
| | | | | | | | | | | | | | Add a function postinst_enable_logging, so that when 'debug-tweaks' is in IMAGE_FEATURES, we create ${sysconfdir}/default/postinst config file, which is sourced by run-postinst scripts to determine whether to log or not, and where to log. [YOCTO #4262] (From OE-Core rev: 99175cabc3936733dd92fac5ebc6f865b864fe92) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added xmlto and dblatex packages for docsScott Rifenbark2013-05-221-4/+4
| | | | | | | | | | These two packages are required for all the supported distros if you are going to build the BitBake manual. (From yocto-docs rev: 76b19462aa1dd850c00b7addccdafcc0f1a67e1c) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel-dev: Updates to "Creating the Append File" section.Scott Rifenbark2013-05-221-4/+11
| | | | | | | | | | | | | | Pointed out by Robert P. J. Day that I was using the wrong FILESEXTRAPATHS example for an append file. I failed to include the "_prepend" part of the variable. Also, the wording based on the example made some assumptions and was not entirely accurate. The changes I put in made the section very specific. Reported-by: Robert P. J. Day <rpjday@crashcourse.ca> (From yocto-docs rev: 659c5a9c41a92f469ea0ea3630e11b4ba2df8f56) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added more detail to note for FILESEXTRAPATHS use.Scott Rifenbark2013-05-221-150/+159
| | | | | | | | | | | | Some discussion about this variable indicated that the importance of the immediate expansion operator was not being called out enough. I added further information to the existing note that states to be sure to use ":=" when using the variable. (From yocto-docs rev: b97d3fa714a7c71356cd00548d3d01280034afc2) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel-dev: Updated changing the configuration section.Scott Rifenbark2013-05-221-15/+27
| | | | | | | | | | | | | | Robert P. J. Day pointed out some implied meanings in this section that indicate configurations from .config are exclusive somehow from configurations applied through config fragments. That is not the case. I have inserted a note to clear up that implied meaning. Reported-by: Robert P. J. Day <rpjday@crashcourse.ca> (From yocto-docs rev: 5ac27e8a2aea662a8e70dda0e852b5ea401b8b00) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added Ubuntu 12.04 (LTS) to list of supported distros.Scott Rifenbark2013-05-221-1/+2
| | | | | | | (From yocto-docs rev: 9452cc3eda50a901682c4c36b8abcc0f556711a7) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation/poky-ent: Updated to essential packages OpenSUSEScott Rifenbark2013-05-221-1/+1
| | | | | | | | | | | | | | | Fixes YOCTO #4468 OpenSUSE 12.3 will not work without the "patch" package. I added this package to the OPENSUSE_HOST_PACKAGES_ESSENTIAL variable in the poky.ent file. This will list that package in both the ref-manual and the yocto-project-qs. Reported-by: Winfried <winfried_mb2@xmsnet.nl (From yocto-docs rev: c2e557fcbe393d6533a3ae7f548a5a25bc5d31f8) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated supported distros listScott Rifenbark2013-05-221-9/+4
| | | | | | | | | | | | | | | | | | In line with our policy of supporting the current and previous releases of host distributions (and additionally the latest LTS release of Ubuntu): * Add Ubuntu 13.04 (released on 25th April) * Remove Fedora 16 * Remove 5.x versions of CentOS * Remove OpenSUSE 11.4 and 12.1 * Remove pre-1.3 versions of Poky Reported-by: Paul Eggleton <paul.eggleton@linux.intel.com> (From yocto-docs rev: 9ae656fb351a7df735f87f99d9823a53774ffb0d) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to removing package management requirementsScott Rifenbark2013-05-221-4/+5
| | | | | | | | | | | | Fixes YOCTO #1706 Applied another set of minor review comments to the section received from Richard Purdie. (From yocto-docs rev: 48aa19b7eea9f4b253cbe86981431ec7dc6d78df) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Applied review comments for eliminating packaging req.Scott Rifenbark2013-05-221-3/+6
| | | | | | | | | | | | | Fixes YOCTO #1706 Richard suggested some technical wording changes. I also added the new sub-section into the introductory material as part of the parent section. (From yocto-docs rev: 201ae16541676365bef69be578433222191eccd3) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Created new section to remove packaging requirementsScott Rifenbark2013-05-221-0/+38
| | | | | | | | | | | | | Fixes YOCTO #1706 Added a new subsection to the section that talks about making a tiny system. The subject matter fits in with reducing a kernel image size. (From yocto-docs rev: 51eb79b88794beaefcb88a4408714a88c9126b2b) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: Updated poky.ent to use 1.5 as YOCTO_DOC_VERSION.Scott Rifenbark2013-05-221-1/+1
| | | | | | | | | | I had "tbd" in there but discovered that that breaks all my manual cross-referencing linking. (From yocto-docs rev: 0b7ca589b4a2b567fd220ba502da1b1f080db2ae) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: Updates to properly build the 1.5 manualsScott Rifenbark2013-05-227-22/+22
| | | | | | | | | | | | | | 1. Changed the variables in poky.ent to contain the "1.5" string and the "tbd" string for the unknowns. 2. Updated the manual revision history tables so to replace the 1.4.1 release entry, which should not be there, to the 1.5 entry. (From yocto-docs rev: d03a09875b1fe0d244b7a7c1bde718319d95a8ab) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: Set up the 1.4.1 manual set.Scott Rifenbark2013-05-227-4/+34
| | | | | | | | | | | 1. Edited poky.ent to have 1.4.1 and 9.0.1 for release stuff. 2. Updated the manual revision tables to have a new entry for 1.4.1 release. (From yocto-docs rev: bd4058b98f93ea5fd5d878f24018ce78b8ce1a53) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bsp-guide: Fixed syntax error in BBLAYERS example.Scott Rifenbark2013-05-221-25/+25
| | | | | | | | | | I fixed this as pointed out by Robert. Reported-by: Robert P. J. Day <rpjday@crashcourse.ca> (From yocto-docs rev: 52eb7d8698ef643150ac0ce987677da7a654b3ea) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual, ref-manual: Minor edits suggested by Bill TraynorScott Rifenbark2013-05-224-12/+14
| | | | | | | | | | Applied some re-wordings as suggested by Bill Traynor. Reported-by: William M.A. Traynor <wmat@alphatroop.com> (From yocto-docs rev: 2510d9795720afc0309a10b18605e5af4a83769b) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bsp-guide, ref-manual: Various fixes from Robert P. J. Day review.Scott Rifenbark2013-05-222-43/+52
| | | | | | | | | | | | | | | | Robert read through the BSP Guide and noted several issues. There were several typos, inacurracies for crown bay code, out-dated kernel usage example, etc. One change I had to make that was related was to fix two cross-reference links to a re-named section. These links were the changes in the FAQ chapter of the ref-manual. Reported-by: Robert P. J. Day <rpjday@crashcourse.ca> (From yocto-docs rev: ae45df660ebf33105ebf5e60e606b0ec76eb9a6d) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual, bsp-guide: Updates for init-ifupdown change.Scott Rifenbark2013-05-222-11/+57
| | | | | | | | | | | | | | | Release 1.4 requires the user to create an append file to the new recipe init-ifupdown if they want to create their own custom /etc/network/interfaces file. Previously, they needed to append the netbase recipe. Changes needed in the migration section of the ref-manual as well as the exmaple used in the bsp-guide. (From yocto-docs rev: 1903df0c21dbc018f0dbb4ce90eac192b428606b) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Review edits applied to selecting init manager section.Scott Rifenbark2013-05-221-125/+133
| | | | | | | | | Applied comments based on Ross Burton's review of this new section. (From yocto-docs rev: d4f5f7b712ea2944efffec9b675341143675efb0) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/bitbake: Handle the case where git isn't installed cleanlyRichard Purdie2013-05-221-4/+5
| | | | | | | | | Currently the user sees ugly errors if git isn't installed, this patch cleans up the code to correctly handle that case. (From OE-Core rev: aeb704fee8b4ffeaeddcdb36ae4e1d62c264ce42) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* task.bbclass: Drop deprecated classRichard Purdie2013-05-221-6/+0
| | | | | | | | Any users have had time to adapt to this change by now, drop the old class. (From OE-Core rev: 9b64b68c93c71c503ef26fa440b974b82438dc88) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* update-alternatives: Drop deprecated code, update to show error messageRichard Purdie2013-05-221-94/+1
| | | | | | | | | This code has been deprecated for a while and confuses the class, lets drop it and just give the user hard error messages instead of the current warnings/fixups. (From OE-Core rev: 72579e1fe49e8bc66c9f5850a2c679ce8941c85d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: Table sorting criteria should not change after deselecting ↵Cristiana Voicu2013-05-223-7/+27
| | | | | | | | | | | | | recipes/packages After a recipe/package is deselected, the table is sorted as before the fadeout animation. [YOCTO #4453] (Bitbake rev: d4968eac539f777367ab1243a1049117cb261176) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: apply a fade out animation when deselecting from tablesCristiana Voicu2013-05-222-34/+30
| | | | | | | | | | | | | | -applied a fade out mechanism for deselctiong on all the tabs of recipes and packages list page -set cursor on the package/recipe when it is included(important when the its place is changing; like when the tree si order by included tab) [YOCTO #4342] (Bitbake rev: 8bd0e0681a6a39c00accbfc0041ab248993f3877) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cookerdata: rename _parse to parse_config_filePaul Eggleton2013-05-221-6/+6
| | | | | | | | | | We use this externally in the OE layer index update script, so it shouldn't really be named as an internal function. (Bitbake rev: 89332a7874e94c8d91ea24200f9739abb1a50397) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: tinfoil: fix for changes to cooker config structurePaul Eggleton2013-05-221-20/+21
| | | | | | | | | | Fix the code here for recent changes to the initialisation of configuration objects for cooker. (Bitbake rev: 9d3ca9aa73a448b0594f03ac8e8317403ec0dc8d) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-layers: fix for move of calc_bbfile_priority within cookerPaul Eggleton2013-05-221-1/+1
| | | | | | | | | | | | calc_bbfile_priority is now in CookerCollectFiles which can be accessed on the collection attribute of a cooker instance. Fixes [YOCTO #4513]. (Bitbake rev: 5d941631ad7198737d9a5c5a920a9062fa0431f8) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: command: Fix function module reference after code rearrangementRichard Purdie2013-05-221-1/+1
| | | | | | (Bitbake rev: ff9f62fd5f76892ad41a5329b75472501e17e712) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: runqueue.py: Ensure export flag is set for fakeroot environment ↵Richard Purdie2013-05-221-0/+1
| | | | | | | | | | | | variables This means the variables show up in the shell execution "run" files since its useful to know what the fakeroot environment is and how to set it up manually. (Bitbake rev: bdf437747b664479acde6deaa9096e2a6bcdf483) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake/cookerdata: Explicitly specify cooker configuration optionsRichard Purdie2013-05-222-12/+21
| | | | | | | | | | | | | | As the code stands today its hard to know which configuration variables are used by which parts of the system. Some are used by the UIs, some by bin/bitbake itself, some by cooker. This patch changes the configuration to just contain the variables cooker uses, and changes bin/bitbake to access the variables it needs directly which hopefully lets us start to untangle this mess. (Bitbake rev: e57497a24b6157c92519a34accd66035a39ad1f8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker: Split configuration parsing code into cookerdataRichard Purdie2013-05-222-118/+139
| | | | | | | | | | | | | | | | | | | In order to have a memory resident bitbake and to allow task execution, we need to be able to rebuild the base configuration without a cooker. This moves the code into its own class so it can be built independently. The interface is less than ideal here but I didn't want to add parsing methods a subclassed DataSmart, at least until we've experimented further with this code and are certain that makes sense. At the very least, the methods are ugly and need cleaning up. Spliting the code out seems to be the right thing to do though and should unblock various activities on BitBake so I believe this code is a step in the right direction. Based on a patch from Alexandru Damian <alexandru.damian@intel.com> (Bitbake rev: 22a0b3cf73d2689db0c118b37aa7492632f8b0a7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker: Move commandline parsing back into the UI/cookerdataRichard Purdie2013-05-229-89/+104
| | | | | | | | | | | | | | | | | | | | | Building up a set of actions for the server is tricky since we depend upon the commandline but fall back to values from the datastore. We should be able to build a datastore without a commandline and vice versa. Ultimately the UI should send the commands to the server. This patch amounts to code rearranging, moving the heavy lifting to the UI, though a helper in the configuration option. This will need further cleanup/tweaking but this should be the only update needed to the UIs. The code now queries the server for any missing data should it need to. This code allows various knowledge of configuration variables to move to the UI side only, partcularly pkgs_to_build but also all the command specifiers. It should also be possible to move cmd eventually, I'm just unsure if any callers call the commands expecting this to default to something sane right now. (Bitbake rev: 2dbbb1d51dafd4451fef8fe16f095bcd4b8f1177) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: Create cookerdata splitting config from cooker and bin/bitbakeRichard Purdie2013-05-224-84/+148
| | | | | | | | | | | | | | | | | | | Currently the UI and server configuration is one big incestuous mess. To start to untangle this we creater cookerdata, a new module which contains various confiuration modules and the code for building the base datastore. To start with we add a ConfigParameters() class which contains information about both the commandline configuration and the original environment. The CookerConfiguration class is created to contain the cooker.configuration options. This means we can transfer new paramters to the server over something like XMLRPC and then build a new configuration from these on the server. Based on a patch from Alexandru Damian <alexandru.damian@intel.com> (Bitbake rev: 35bd5997e8d8e74bc36019030cc10c560a8134f9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bin/bitbake: Improve exception handlingRichard Purdie2013-05-221-2/+3
| | | | | | | | | | Due to the internal event processing, this excepting handler usually raises an Empty error, masking the underlying failure. Ensure the original exception is raised. (Bitbake rev: 7d548568a55adfe84a976f2a549995e42da1afef) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-18 03:35:00 +0000