summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* binutils: refactor packages for staticdevSaul Wold2012-01-242-2/+1
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* eglibc: refactor packages for staticdevSaul Wold2012-01-241-3/+6
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* opkg: refactor packages for staticdevSaul Wold2012-01-241-3/+4
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* opkg: move common code & metadata into opkg.inc to reduce code duplicationSaul Wold2012-01-243-85/+44
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* tcp-wrappers: refactor packages for staticdevSaul Wold2012-01-241-4/+5
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* syslinux: refactor packages for staticdevSaul Wold2012-01-241-2/+3
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* libtool: refactor packages for staticdevSaul Wold2012-01-241-4/+5
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* gstreamer: refactor packages for staticdevSaul Wold2012-01-243-7/+9
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* tiff: refactor packages for staticdevSaul Wold2012-01-241-3/+4
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* mpeg2dec: refactor packages for staticdevSaul Wold2012-01-241-4/+6
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* apr-util: refactor packages for staticdevSaul Wold2012-01-241-2/+2
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* sqlite3: refactor packages for staticdevSaul Wold2012-01-242-3/+5
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* libxft: refactor packages for staticdevSaul Wold2012-01-241-6/+1
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* sysfsutils: refactor packages for staticdevSaul Wold2012-01-241-4/+5
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* libsoup: refactor packages for staticdevSaul Wold2012-01-241-4/+4
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* augeas: refactor packages for staticdevSaul Wold2012-01-242-4/+5
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* avahi-ui: refactor packages for staticdevSaul Wold2012-01-241-3/+4
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* apmd: refactor packages for staticdevSaul Wold2012-01-241-4/+5
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* Fix Upstream-Status entriesSaul Wold2012-01-249-7/+11
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* documentation-audit.sh: remove COMMERCIAL_LICENSE warningTom Zanussi2012-01-241-1/+2
| | | | | | | | COMMERCIAL_LICENSE no longer exists; the equivalent functionality is now has been replaced by LICENSE_FLAGS_WHITELIST, so replace the COMMERCIAL_LICENSE warning with a similarly equivalent warning. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
* default-distrovars.inc: remove COMMERCIAL_LICENSE et alTom Zanussi2012-01-241-5/+0
| | | | | | | The global COMMERCIAL_LICENSE mechanism has been obsoleted by per-recipe LICENSE_FLAGS, so remove the related variables. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
* base.bbclass: replace COMMERCIAL_LICENSE code with LICENSE_FLAGS codeTom Zanussi2012-01-241-6/+6
| | | | | | | | The COMMERCIAL_LICENSE mechanism has been superseded by LICENSE_FLAGS so remove the code that implements COMMERCIAL_LICENSE and replace it with the corresponding LICENSE_FLAGS version. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
* Add LICENSE_FLAGS to packages mentioned in COMMERCIAL_LICENSETom Zanussi2012-01-248-0/+9
| | | | | | | | | | | | | | | | Per-recipe LICENSE_FLAGS replace the global COMMERCIAL_LICENSE list; add LICENSE_FLAGS varables to each the recipes mentioned in that list: - lame - gst-fluendo-mp3 - gst-openmax - gst-plugins-ugly - libmad - libomxil - mpeg2dec - qmmp Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
* license.bbclass: add support for LICENSE_FLAGSTom Zanussi2012-01-241-0/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | LICENSE_FLAGS are a per-recipe replacement for the COMMERCIAL_LICENSE mechanism. In the COMMERCIAL_LICENSE mechanism, any package name mentioned in the global COMMERCIAL_LICENSE list is 'blacklisted' from being included in an image. To allow the blacklisted package into the image, the corresponding packages need to be removed from the COMMERCIAL_LICENSE list. This mechanism relies on a global list defined in default-distrovars.inc. The LICENSE_FLAGS mechanism essentially implements the same thing but turns the global blacklist into a per-recipe whitelist. Any recipe can optionally define one or more 'license flags'; if defined, each of the license flags defined for a recipe must have matching entries in a global LICENSE_FLAGS_WHITELIST variable. The definition of 'matching' is simple, but there are a couple things users need to know in order to correctly and effectively use it. Before we test a flag against the whitelist, we append _${PN} to it, thus automatically making each LICENSE_FLAG recipe-specific. We then try to match that string against the whitelist. So if the user specifies LICENSE_FLAGS = 'commercial' for recipe 'foo', the string 'commercial_foo' should be specified in the whitelist in order for it to match. However, the user can also broaden the match by putting any '_'-separated beginning subset of a LICENSE_FLAG in the whitelist, which will also match e.g. simply specifying 'commercial' in the whitelist would match any expanded LICENSE_FLAG starting with 'commercial' such as 'commercial_foo' and 'commercial_bar' which are the strings that would have been automatically generated if those recipes had simply specified LICENSE_FLAGS = 'commercial' This allows for a range of specificity for the items in the whitelist, from more general to perfectly specific. So users have the choice of exhaustively enumerating each license flag in the whitelist to allow only those specific recipes into the image, or of using a more general string to pick up anything matching just the first component(s). Note that this scheme works even if the flag already has _pn appended - the extra _pn is redundant, but doesn't affect the outcome e.g. a license flag of 'commercial_1.2_foo' would turn into 'commercial_1.2_foo_foo' and would match both the general 'commercial' and the specific 'commercial_1.2_foo' as expected (it would also match commercial_1.2_foo_foo' and 'commercial_1.2', which don't make much sense as far as something a user would think of specifying in the whitelist). For a versioned string, the user could instead specify 'commercial_foo_1.2', which would turn into 'commercial_foo_1.2_foo', but which would as expected allow the user to pick up this package along with anything else 'commercial' by specifying 'commercial' in the whitelist, or anything with a 'commercial_foo' license regardless of version by using 'commercial_foo' in the whitelist, or 'commercial_foo_1.1' to be completely specific about package and version. The current behavior of COMMERCIAL_LICENSE is replicated as mentioned above by having the current set of COMMERCIAL_LICENSE flags implemented using LICENSE_FLAGS = "commercial". That being the case, the current COMMERCIAL_LICENSE can equivalently be specified in the new scheme by putting the below in local.conf: # This is a list of packages that require a commercial license to ship # product. If shipped as part of an image these packages may have # implications so they are disabled by default. To enable them, # un-comment the below as appropriate. #LICENSE_FLAGS_WHITELIST = "commercial_gst-fluendo-mp3 \ # commercial_gst-openmax \ # commercial_gst-plugins-ugly \ # commercial_lame \ # commercial_libmad \ # commercial_libomxil \ # commercial_mpeg2dec \ # commercial_qmmp" The above allows all of the current COMMERCIAL_LICENSE packages in - to disallow a particular package from appearing in the image, simply remove it from the whitelist. To allow them all in, you could also specify LICENSE_FLAGS_WHITELIST = "commercial". Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
* core-image-foo: add description to each image bb fileShane Wang2012-01-2414-1/+40
| | | | | | Add DESCRIPTION to each image bb file according to poky reference manual for Hob2 use later. Signed-off-by: Shane Wang <shane.wang@intel.com>
* initscripts: remove space from shebang, just cosmeticsMartin Jansa2012-01-2410-10/+10
| | | | | | | * at least in initscripts it's consistent now Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: add shebang where it was missing completelyMartin Jansa2012-01-247-0/+7
| | | | | Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimage-testlib: rename qemuppc imageSaul Wold2012-01-241-2/+2
| | | | | | | | A recent set of changes changed the kernel name from bzImage to vmlinux, this test needs to change also. Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/qemuppc: fix console and ethernetBruce Ashfield2012-01-243-3/+3
| | | | | | | | | | | | | | | Two issues are fixed with this commit, the ability to use the keyboard on a graphical qemu boot and enabling ethernet by default on a 3.0 kernel. The keyboard is fixed via the same method as the other simulations with the addition of console=tty on the qemu command line. Ethernet is fixed by adding a dependency of PCNET32 to the qemuppc configuration, which allows us to build ethernet directly into the image. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc_4.6.bb: Drop duplicated SRC_URI componentRichard Purdie2012-01-241-2/+0
| | | | | | | This was duplicated from the main SRC_URI and was causing incorrect task signatures. This simply removes the duplication. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-package-cross.inc: Mark do_package* tasks as noexecRichard Purdie2012-01-231-0/+5
| | | | | | | These tasks don't do anything, this just avoids the overhead of forking to exec them. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Switch to the OEBasic signature generatorRichard Purdie2012-01-231-2/+1
| | | | | | | | | This signature generator will allow easier customisation of which task dependencies get included in the signatures using the code in lib/oe/sstatesig.py. Compared the the regexp, this function is much easier to understand and customise. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe: Add sstatesig, OE specific signature generator classesRichard Purdie2012-01-232-1/+49
| | | | | | | | | | | | | This patch adds SignatureGenerator classes specific to OE. For now, these emulate the previous behaviour with the exception that dependencies on quilt-native are now ignored for checksum purposes. The intent is to allow easier experimentation and customisation of this code in future as a result of these changes. Note that these changes require pending bitbake patches. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity.conf: Incrase bitbake minimum version requirement to 1.15.1Richard Purdie2012-01-231-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Ensure that the shared source directory shared the same sstate hashesRichard Purdie2012-01-234-17/+18
| | | | | | | | | | | | | | | | | | | | The fetch/unpack/patch/headerfix tasks are shared and hence their sstate hashes should also match. Sadly this is not the case since: a) gcc-runtime applies an additional patch b) The do_headerfix task was missing from libgcc c) The do_headerfix task is a shell task and hence depends on all exported variables which can vary between cross and target recipes. To fix this, the patch moves the patch to the common code, adds the headerfix task to a common include file and disabled shell dependencies on the do_headerfix task since its clear in this case we don't need thsoe dependencies since we just call sed. With this patch applied, all these recipes now share common sstate checksums. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* distro_tracking: update libpng, libgdbus, opensp, nfs-utils manual check datesScott Garman2012-01-201-8/+11
| | | | | Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildhistory_analysis: include related fields in outputPaul Eggleton2012-01-191-25/+64
| | | | | | | | | | | | | | | | | | | | | | | | | Sometimes, when a value changes in the buildhistory it is useful to know when a related (but not necessarily itself monitored) value changes as it can help explain the change. For example, when the list of installed packages for an image changes it could be caused by a change to one of the image-related variables. Related field changes are recorded as sub-items of each change. Currently the only way to visualise these is via the buildhistory-diff tool, so an example would be: Changes to images/qemux86/eglibc/core-image-minimal (installed-package-names.txt): locale-base-de-de was added procps was added * IMAGE_LINGUAS: added "de-de" * IMAGE_INSTALL: added "procps" Here we see that two additional packages have been added to the image, and looking at the related changes to the two variables IMAGE_INSTALL and IMAGE_LINGUAS we have the explanation as to why. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/patch: avoid backtrace when patch does not applyPaul Eggleton2012-01-192-6/+9
| | | | | | | | | | | | We don't need to see a Python stack backtrace when a patch does not apply, just the error output from patch, so trap these kinds of errors and ensure that we display the message and fail the task and nothing else. Fixes [YOCTO #1143] Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* task-base: rename VIRTUAL-RUNTIME-alsa-state to use underscoreMartin Jansa2012-01-192-2/+2
| | | | | | | | | | * in http://lists.linuxtogo.org/pipermail/openembedded-core/2012-January/016226.html we talked about VIRTUAL-RUNTIME_alsa-state, but VIRTUAL-RUNTIME-alsa-state was used instead, which is inconsistent with other VIRTUAL-RUNTIME vars Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* hdparm: remove PRIORITYPaul Eggleton2012-01-191-1/+0
| | | | | | | | | PRIORITY is no longer set in recipes in OE-Core, so remove it. (Since "optional" is the default value from bitbake.conf, no PR bump is necessary.) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildhistory_analysis: improve field handling robustnessPaul Eggleton2012-01-191-10/+19
| | | | | | | | | | | | | | | Avoid errors when comparing changes for KEY = value files (package info files and image-info.txt): * Handle keys appearing and disappearing - this will help to handle PE in package info files (which is only written when it is not blank) and when we add additional fields in future. * Handle when old value is 0 for numeric field (avoid division by zero) * Report when numeric field was empty or missing rather than 0 (but still treat it as 0 for comparison purposes) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildhistory_analysis: correctly handle whitespace when splitting listsPaul Eggleton2012-01-191-2/+2
| | | | | | | | | | Don't specify any argument to the split() function when handling changes to list type variables (e.g. PACKAGES) so that the values are split by any whitespace and only split once for a block of multiple whitespace characters. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildhistory: record additional image infoPaul Eggleton2012-01-192-22/+47
| | | | | | | | | | | | | | | Record some additional information about images - the uncompressed size of the final image as well as the values of various variables that may have influenced its contents. This is recorded in a machine-readable "image-info.txt" file similar in structure to the package history files. Also add some code to analyse changes to these values. (Most of the variable values aren't monitored directly but will be used as contextual information when they change at the same time as the content of the image changing.) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* grub-efi-native: fix errors with automake 1.11.2Nitin A Kamble2012-01-192-5810/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit replaces earlier patch (grub-1.99_fix_for_automake_1.11.2.patch) which did not work on all distros. Fixes these errors observed with automake 1.11.2 The useof pkglibhas become more strict compared to the earlier release of automake resulting in these failures. Fixed the files related to automake to avoid the issue. | conf/Makefile.common:140: `pkglibdir' is not a legitimate directory for `DATA' | grub-core/Makefile.am:5: `conf/Makefile.common' included from here | conf/Makefile.common:140: `pkglibdir' is not a legitimate directory for `DATA' | Makefile.am:6: `conf/Makefile.common' included from here | autoreconf: automake failed with exit status: 1 | ERROR: autoreconf execution failed. | conf/Makefile.common:150: `pkglibdir' is not a legitimate directory for `SCRIPTS' | grub-core/Makefile.am:5: `conf/Makefile.common' included from here | conf/Makefile.common:140: `pkglibdir' is not a legitimate directory for `DATA' | grub-core/Makefile.am:5: `conf/Makefile.common' included from here | conf/Makefile.common:150: `pkglibdir' is not a legitimate directory for `SCRIPTS' | Makefile.am:6: `conf/Makefile.common' included from here | conf/Makefile.common:140: `pkglibdir' is not a legitimate directory for `DATA' | Makefile.am:6: `conf/Makefile.common' included from here | autoreconf: automake failed with exit status: 1 Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
* autogen-native: new recipe for grub-efi-nativeNitin A Kamble2012-01-191-0/+24
| | | | | | | | | | | | | grub-efi-native build is failing due to missing autogen command. Hence created this recipe. The newer versions of autogen 5.13 & 5.14 both are dumping core while building from source, so going back to the working 5.12 version. Also noticed that no distro vendor has picked up 5.13 or 5.14 versions of autogen yet. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
* guile: new recipe for autogenNitin A Kamble2012-01-196-0/+249
| | | | | | | | | guile recipe is needed by autogen. Imported & updated the guile-cross-config generation & guile-2.0.pc manipulation code from the meta-oe guile recipe. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
* libunistring: new recipe for autogenNitin A Kamble2012-01-191-0/+28
| | | | | | | libunistring recipe is needed by guile. And guile is needed by autogen. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
* bdwgc: new recipe for autogenNitin A Kamble2012-01-191-0/+37
| | | | | | | | | | | | This recipe is needed by guile. And guile is needed for autogen. As per Beth's recommondation changed the license specification of the recipe as LICENSE = "MIT & FSF-Unlimited & GPL-2.0" Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
* enchant: refactor packages for staticdevSaul Wold2012-01-191-2/+3
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* boost: refactor packages for staticdevSaul Wold2012-01-191-3/+4
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
generated by cgit v1.2.3 (git 2.46.0) at 2024-11-20 08:18:11 +0000