summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* systemd: skip in non-systemd distros to fix world buildsRoss Burton2013-01-211-0/+8
| | | | | | | (From OE-Core rev: a2553b5f8b80ca0cd578afa2d2857ebb2b70ee3c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: BBHandler/ConfHandler: Merge fix for multiline commentsRichard Purdie2013-01-212-2/+2
| | | | | | | | | | This was meant to be squashed into the previous commit for multiline comment handling. It fixes the case the commented multiline is followed by an empty line which was resulting in a traceback instead of a sane error message. (Bitbake rev: 7e7d692e244fe8dca533f842ca143b9c821e317c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: BBHandler/ConfHandler: Improve multiline comment handlingRichard Purdie2013-01-212-4/+14
| | | | | | | | | | | | | | | | | | | | Faced with an expression like: # Some comment \ FOO = "bar" what should bitbake do? Technically, the \ character means its multiline and currently the code treats this as a continuation of the comment. This can surprise some people and is not intuitive. This patch makes bitbake simply error and asks the user to be clearer about what they mean. (Bitbake rev: 589d31ce41e019ee6a7cb6527d67bc76c0b6382a) (Bitbake rev: 79c00fabe08b4c210a3bd81cfaffbc47ffdc2e2b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dbus: upgrade to 1.6.8Cristian Iorga2013-01-218-8/+8
| | | | | | | | | | dbus, dbus-ptest upgraded to v1.6.8 (From OE-Core rev: 272661a7fca7e0ee8f6b0d7a4ba97f09a82a540e) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boost: Upgrade 1.51 -> 1.52Khem Raj2013-01-214-58/+9
| | | | | | | | | Drop hash_enums.patch which is already applied upstream (From OE-Core rev: c4d3f5596662d6aced46f270f566b510a36e4952) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk+3: refresh cross.patchRoss Burton2013-01-211-27/+36
| | | | | | | | | | cross.patch was accepted upstream, so update this patch with the commit that was merged. (From OE-Core rev: 8e5ffa370c4259f925a0454fe7fd81c80ef2174b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bb-matrix: Fix min and max calculationsDarren Hart2013-01-212-7/+10
| | | | | | | | | | | | | | | | The BB and PM ranges were originally intended to use leading 0s to ensure all the values were the same string length, making for nice log filenames and columnar dat files. However, not everyone will do this - especially if it isn't documented. Document the intent. Make the generation and parsing of dat files robust to either method. (From OE-Core rev: 90dc44c8246f2a580fe4a41ce28c201e52307500) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofile: backport patches to fix ppc build issuesMatthew McClintock2013-01-215-2/+357
| | | | | | | | | | | | | | | | | | | Fixes: | operf_utils.cpp: In function 'bool _op_get_event_codes(std::vector*)': | operf_utils.cpp:151:21: error: 'pfm_initialize' was not declared in this scope | operf_utils.cpp:151:26: error: 'PFM_SUCCESS' was not declared in this scope | operf_utils.cpp:166:45: error: 'PFM_PLM3' was not declared in this scope | operf_utils.cpp:166:55: error: 'PFM_OS_NONE' was not declared in this scope | operf_utils.cpp:166:72: error: 'pfm_get_os_event_encoding' was not declared in this scope | operf_utils.cpp:167:14: error: 'PFM_SUCCESS' was not declared in this scope [YOCTO #3717] (From OE-Core rev: 121cb96964fe2f374d814bf39036119bd63b9589) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: drop unnecessary and broken packages.remove()Christopher Larson2013-01-211-1/+0
| | | | | | | (From OE-Core rev: 5480371d0473482437ce4350e6593f006101ef40) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofile: set correct kernel pathBogdan Marinescu2013-01-201-2/+2
| | | | | | | | | | | oprofile's "configure" was always looking at the configuration of the host kernel, not the target kernel. This patch instructs oprofile to use the target kernel to configure itself. (From OE-Core rev: 5892db9a34c188b8a9bdaa86e19ba62a7f4793b5) Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm2cpio: Update to match rpm4 specs for decompressionSaul Wold2013-01-201-26/+14
| | | | | | | | | [YOCTO #3753] (From OE-Core rev: 1377278187d20853304fe2689105f2848d796d86) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* update-alternatives: Add a build-time dependencyMark Hatle2013-01-202-1/+14
| | | | | | | | | | | | | | | | | | | We need to add a build time dependency on virtual/update-alternatives, however we can't just do DEPENDS +=, or we end up with various problems. To work around this, in the anonymous python space we ensure we only do the addition when the package does not provide virtual/update-alternatives and it is a target package. Also the system wide PREFERRED_PROVIDER was incorrect. It references a runtime package, and not the recipe it should have. This has been corrected. [YOCTO #3691] (From OE-Core rev: 56a59ef12936dcc6464cf1d43dda6957a5aa8c65) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Tested-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_rpm: Re-add a few system provides to the SDKMark Hatle2013-01-201-1/+3
| | | | | | | | | | | | | | When building the target SDK portion, we can safely ignore various package rdepends. These dependencies are not required on a build only environment like an SDK. [YOCTO #3691] (From OE-Core rev: 1edd44bed9e9829f7c2466928bc3f45be102b84b) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Tested-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/lib/bsp/engine.py: add handling for JSON stringsTom Zanussi2013-01-201-4/+7
| | | | | | | | | | | | | | | | | Normally pre-canned properties are supplied as JSON from a file, which the user can specify using e.g. the -i option. We can reuse that basic functionality for dedicated command-line parameters by sythesizing a JSON string containing those param values on the fly and passing that in instead. This adds the ability for the common creation code to accept JSON strings as well as JSON files. (From meta-yocto rev: 5a2e840b24822e018de94ec4f554363b59c4e8bd) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-layer: add optional layer priority paramTom Zanussi2013-01-202-4/+19
| | | | | | | | | | | If the user specifies a layer priority following the layer name, layer creation will proceed without further queries using the specified layer priority and the remaining values defaulted. (From meta-yocto rev: 84a0bd8940f82fb938972d7b026367d40c9472e7) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/lib/bsp/engine.py: refactor bsp-creation codeTom Zanussi2013-01-201-65/+76
| | | | | | | | | | | | | This does a bit of refactoring of the bsp-generation code to make it generically reusable for generating non-bsp layers. The first user remains the existing yocto-bsp tool; these changes allow a second user, the new yocto-layer tool, to use the same code. (From meta-yocto rev: 1527a0ee7bce08a527c9d80516531b17816dff17) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-layer: add 'layer' template dataTom Zanussi2013-01-209-0/+168
| | | | | | | | | | Add a 'layer' target containing all the data that will be used to generate a generic yocto layer. (From meta-yocto rev: 198a85f61ebd6435830285b2a9b1b925aea6779e) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-layer: add help/usageTom Zanussi2013-01-201-0/+228
| | | | | | | | | This is essentially 'the documentation' for the yocto-layer tool. (From meta-yocto rev: 34229b931bad8fc0e4d4431bb5cb46fccbea03bf) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-layer: new scriptTom Zanussi2013-01-201-0/+142
| | | | | | | | | | Implementation of the 'yocto-layer' command-line tool, for creating generic layers and listing their input properties. (From meta-yocto rev: 8170bea55379d1a25acc0fea108675526eeab6f6) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/lib/bsp/engine.py: add yocto_layer_create()Tom Zanussi2013-01-201-0/+56
| | | | | | | | | | Add a new yocto_layer_create() function that will be used to generate a generic yocto layer (for the new 'yocto-layer' command). (From meta-yocto rev: 44acd01bf47c2e0a777e686c9339a6ff951fc972) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* attr: convert to generic syscall numbersRiku Voipio2013-01-202-1/+190
| | | | | | | | | | | | | xattr system calls are old enough that we can switch to just pulling the system call numbers from kernel headers. Upstream-Status: Submitted acl-devel@nongnu.org (From OE-Core rev: 4dab91a4109a452f43483ef11ea9037ca8df1b33) Signed-off-by: Riku Voipio <riku.voipio@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nspr: add aarch64 supportRiku Voipio2013-01-202-0/+102
| | | | | | | | | | | Add needed defines for Aarch64 support. Upstream-Status: Submitted https://bugzilla.mozilla.org/show_bug.cgi?id=827271 (From OE-Core rev: 53b4f10bf7e8e83275a64da6700a52c5a4ba533d) Signed-off-by: Riku Voipio <riku.voipio@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky-bleeding: Ensure poky overrides are appliedRichard Purdie2013-01-201-0/+1
| | | | | | (From meta-yocto rev: 79d8d084f1053041540355c0712643be91c21905) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Added DISTRO var to poky-bleeding conf fileCristiana Voicu2013-01-201-0/+2
| | | | | | | | | | | | -noticed in Hob that when DISTRO was set to poky-bleeding, it was not saved; it was overriten by "poky" [YOCTO #3670] (From meta-yocto rev: 9295b3f89b81a52b2693ae97edb1a4467c630e5f) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk-directfb: rename to directfbConstantin Musca2013-01-204-4/+4
| | | | | | | | | | | | | - core-image-gtk-directfb has been renamed to core-image-directfb - packagegroup-core-gtk-directfb has been renamed to packagegroup-core-directfb - DirectFB is not supported by gtk versions >= 2.18 (From meta-yocto rev: 545b3fdebc0d4d5e5bf2e56eab2288a5c4282e9e) Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Modified meta-yocto/conf/distro/include/package_regex.incEmilia Ciobanu2013-01-201-11/+11
| | | | | | | | | | Removed all *alpha*, *beta*, *rc* from regexes. (From meta-yocto rev: 49ec9a8abfff5a29296681b81c1ca8d35039bc3b) Signed-off-by: Emilia Ciobanu <emilia.maria.silvia.ciobanu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng: update references to legacy lttng recipesTom Zanussi2013-01-203-8/+3
| | | | | | | | | | | | | 'legacy' lttng was removed, so we need to remove the references to the legacy lttng recipes, namely lttng-control and lttng-viewer. Also update recipe_color to add entries for the new lttng-2.0 recipes lttng-modules, lttng-tools, and babeltrace, to maintain consistency. (From meta-yocto rev: ce68fe95471200261e1ac968f63ae82020ac8871) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: updated package ownersBogdan Marinescu2013-01-201-2/+2
| | | | | | | | | | | | The linux-libc-headers and linux-libc-headers-yocto packages are currently maintained by Bruce Ashfield. The maintainers.inc file was updated with this information. (From meta-yocto rev: 37e2db30e957fa2b0e515813e678b557fafadc8c) Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/meta-yocto: update hardware reference BSPs to 3.4.26 and LTSIBruce Ashfield2013-01-201-4/+5
| | | | | | | | | | Bumping the yocto reference BSPs to pickup the latest oe-core 3.4.26, -rt and LTSI updates. (From meta-yocto rev: fa7adfafb521e7de81beebd4525a5d2ce1763dc3) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cpan_build: Fix bashismRichard Purdie2013-01-201-1/+1
| | | | | | | | | Fix a build failure caused by a bashism and improve quoting whilst in the area. (From OE-Core rev: 9eb78340c61acddb0c2012e25c76c18735febb4d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool-cross: Add missing libltdl components to installRichard Purdie2013-01-201-0/+3
| | | | | | | | | Without this some software fails to build complaining it can't find these utilities. (From OE-Core rev: db84eaf851b22b262d9dc48eb55bd5224a00fdd2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* liburi-perl: Add BBCLASSEXTEND for native versionRichard Purdie2013-01-201-0/+2
| | | | | | (From OE-Core rev: cac29d930910c257293ed2165faa5397f0a5d07c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: Fix shlibs cross package-arch contaminationRichard Purdie2013-01-201-2/+4
| | | | | | | | | | | | | | | I found that if I had two packages architectures built (say core2 and i586), that the shlibs data from i586 was being used in the core2 build. This lead to odd dependency issues if the i586 build was out of date and core2 was being targetted. When loading shlibs files, the last loaded wins so we need to iterate the lists from least to strongest weighting, not the other way around. With this patch applied, the contamination issue is resolved. (From OE-Core rev: acd7b1c2ee9f3ff84c45a723dba5e0bc5f6a100c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dropbear: Deal with truncated host keys by removing themHolger Hans Peter Freyther2013-01-202-1/+7
| | | | | | | | | | | | Dropbear does not start when the host key is empty and it is possible that a device is switched off before the host key is generated. This is possible because the dropbearkey code doesn't create a temporary file first. Detect truncated keys and then remove them which will lead to the re-generation. This way the dropbear process will always start. (From OE-Core rev: 16b57e352f5844f301cc6c7ea4f87bf750c11d67) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_base.bbclass: Work around bugs with gnu tar < 1.24Jason Wessel2013-01-201-3/+2
| | | | | | | | | | | | | | | | | | | | | | | The gnu tar versions less than 1.24 pose a problem with the SDK extraction. A typical SDK will have hard links. The SDK is created with a newer version of tar but extracted with the host version of tar which may be much older. The specific defect is that older version of gnu tar do not properly handle the "--strip-components=" argument when processing hard links and the paths do not get properly truncated and hooked up with the corresponding real file payloads. This leads to errors like the following during the SDK install: tar: sysroots/qemux86-yocto-linux/usr/bin/getconf: Cannot hard link to `./opt/yocto/SDK-qemux86/sysroots/qemux86-yocto-linux/usr/bin/POSIX_V6_ILP32_OFFBIG': No such file or directory The simple way to work around the problem is to just not save the path information that is going to get chopped off anyway. This has the added benefit that it saves a small amount of space in the tar archive as well. (From OE-Core rev: 0f4112016bac07f0294f2a4d0fde4659c0fed2d2) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: replace AUTOINC directly in PKGVEnrico Scholz2013-01-201-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | b27b438221e16ac3df6ac66d761b77e3bd43db67 introduced a regression when PKGV is modified by the recipe. E.g. when having something like | PV = "1.7.33+gitr${SRCPV}" | PKGV = "1.7.33+gitr${GITPKGV}" | RDEPENDS_${PN}-subpkg += "${PN} (= ${EXTENDPKGV})" | inherit gitpkgv The resulting core package has | Version: 1.7.33+git234+cd01e8c-r11 and because the subpackage has | Depends: vdr (= 1.7.33+git0+cd01e8c18d494150730214f033f84e5282ce7639-r11) image build fails with | * satisfy_dependencies_for: Cannot satisfy the following dependencies ... | * vdr (= 1.7.33+git0+cd01e8c18d494150730214f033f84e5282ce7639-r11) Patch avoids the 'PKGV = "cleanup(${PV})"' operation and replaces AUTOINC directly within PKGV. This might introduce a regression too when 'AUTOINC' is added to PKGV intentionally but impact is small and can be fixed trivially by using another string. (From OE-Core rev: 6e46664085fa49bc204fc944ca23ed6383e2ec51) Signed-off-by: Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de> Cc: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: update intel graphics features/configsBruce Ashfield2013-01-203-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | Updating the meta branch to import the following commits that cleanup and reorganize the features that make up the graphics features of the Intel BSPs c0b3904 meta: add config fragment for gma600 graphics driver f41638f meta: add config fragment for gma500 graphics driver ff8ad3e meta: sys940x: drop vesa fragment from bsp config fcb82ac meta: sys940x: remove emgd config from bsp config c1677bb meta: fri2: drop vesa fragment from bsp config 7324440 meta: fri2: remove emgd config from bsp config dd435c6 meta: emenlow: drop vesa fragment from bsp config 243b515 meta: emenlow: remove emgd config from bsp config 3e1be82 meta: crownbay: drop vesa fragment from bsp config fc5ed4e meta: crownbay: remove emgd config from bsp config d46236b meta: drm-emgd.cfg: add configs for dependent routines db4bc5e meta: relocate git-merge of emgd branch (From OE-Core rev: 8d0074ef2b61bf022ed1bb3b5f1afe526d8c921b) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: update to 3.4.26 and 3.4.25-rt37Bruce Ashfield2013-01-203-15/+15
| | | | | | | | | | Updating the yocto 3.4 kernel tree to the 3.4.25 and 3.4.26 -stable updates as well as refreshing the preempt-rt branches to 3.4.25-rt37. (From OE-Core rev: da536703bdcf31c8c2ef17f5a49d06280fe77600) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* consolekit_0.4.5.bb: Package unpackaged systemd filesKhem Raj2013-01-201-1/+1
| | | | | | | (From OE-Core rev: 8ac35f3bba5d00549f5255acf17a8be914402d50) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel.bbclass, module-base.bbclass: Use CC to form KERNEL_CCKhem Raj2013-01-203-31/+14
| | | | | | | | | | | | | | | | | | | kernel compiler is not special and we currently have it so we want to pass -march and -mtune options as CFLAGS to kernel build so that compiler picks the right subarch flags when compiling assembly files in particular. Otherwise defaults are chosen which may not be right in many case e.g. when compiling kernel for collie machine we should use arch=armv4 but it uses toolchain/as defaults which is armv5te in some case e.g. thumb1 we know that kernel can not be compiled in thumb1 mode so we can provide that information e.g. -marm option through KERNEL_HOST_CC_ARCH variable as we do now (From OE-Core rev: c49f967384ccbfe131bbb33ee518014f3fc4b38f) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libpam: register PAM session with logindKoen Kooi2013-01-201-1/+3
| | | | | | | | | | | This make screen/tmux/etc work as intended. (From OE-Core rev: 58731bbdbd4ab4cfd560f14758a65efdfad2e28f) Signed-off-by: Martin Donnelly <martin.donnelly@ge.com> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-boot: only install initscripts if we're using sysvinitRoss Burton2013-01-201-2/+2
| | | | | | | (From OE-Core rev: 9e7c64ca9afbf27edd0d35a1830ce55ee6d778ab) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base-files: add fstab for systemd based systemsMartin Donnelly2013-01-202-1/+15
| | | | | | | | | | | | | The default fstab has entries which are not necessary in systemd based systems so add a simpler default in this case. (From OE-Core rev: 77bbb839ba25b974a538b90d346b454ccd5deefd) Signed-off-by: Martin Donnelly <martin.donnelly@ge.com> Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* update-rc.d: disable update-rc.d.bbclass when systemd enabledRadu Moisan2013-01-202-89/+90
| | | | | | | | | | | update-rc.d is not necessary when systemd is enabled, systemctl is the replacement (From OE-Core rev: eaa82c842d3197e0251a887ba16028c22f9d8d94) Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-boot: install systemd-compat-units on systemd imagesRoss Burton2013-01-201-0/+1
| | | | | | | | | systemd-compat-units is needed to run postinsts for example. (From OE-Core rev: cf783377767c70db544da57593616cfc952dbfb9) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers: Add systemd option to PREFERRED_PROVIDER_udevRadu Moisan2013-01-201-1/+1
| | | | | | | | (From OE-Core rev: fb8e5285bbc6d5aac5d4103c0a983b7b6c54d73d) Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: add systemd recipesRadu Moisan2013-01-2022-0/+1597
| | | | | | | | | | | | | | | | | | | Add systemd recipes and associated support recipes. Mostly based on meta-oe/meta-systemd, so almost all credit should go to: Andreas Müller <schnitzeltony@googlemail.com> Denis 'GNUtoo' Carikli <GNUtoo@no-log.org> Holger Hans Peter Freyther <holger@moiji-mobile.com> Khem Raj <raj.khem@gmail.com> Koen Kooi <koen@dominion.thruhere.net> Martin Jansa <Martin.Jansa@gmail.com> (From OE-Core rev: 6a8a48b4d0d0b9b8d8af46cae11245bcb870bbc3) Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dbus: respect systemd distro featureRoss Burton2013-01-201-13/+14
| | | | | | | | | | Only configure for systemd if we are using systemd, and remove the dbus-systemd package by putting the service files into PN itself. (From OE-Core rev: 06e262c9b4c406b886db6ca8eee55ab441599151) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers: Automatically set PREFERRED_PROVIDER_udevRadu Moisan2013-01-201-0/+1
| | | | | | | | | | | | | This is a more generic way to set preferred provider for udev. We expect to have multiple choices once we integrate other init managers, and this way we can automatically set it considering distro settings. (From OE-Core rev: da13562af73d144b5782ee8d755e2249cd9d2d8c) Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-distrovars: Add DISTRO_FEATURES_INITMAN to DISTRO_FEATURESRadu Moisan2013-01-202-2/+3
| | | | | | | | | | | | | | This is a more generic way to set the init manager since we plan to support other init managers as well. I will use this variable as a switch to turn on/off any init scheme that we might support in the future. By default we use sysvinit. (From OE-Core rev: 87f06346728bda000c0c0f95312b6a0a1b149ab4) Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-16 16:30:18 +0000