summaryrefslogtreecommitdiffstats
path: root/recipes-core/initscripts
Commit message (Collapse)AuthorAgeFilesLines
* global: overrides syntax conversionBruce Ashfield2021-08-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | OEcore/bitbake are moving to use the clearer ":" as an overrides separator. This is pass one of updating the meta-virt recipes to use that syntax. This has only been minimally build/runtime tested, more changes will be required for missed overrides, or incorrect conversions Note: A recent bitbake is required: commit 75fad23fc06c008a03414a1fc288a8614c6af9ca Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Sun Jul 18 12:59:15 2021 +0100 bitbake: data_smart/parse: Allow ':' characters in variable/function names It is becomming increasingly clear we need to find a way to show what is/is not an override in our syntax. We need to do this in a way which is clear to users, readable and in a way we can transition to. The most effective way I've found to this is to use the ":" charater to directly replace "_" where an override is being specified. This includes "append", "prepend" and "remove" which are effectively special override directives. This patch simply adds the character to the parser so bitbake accepts the value but maps it back to "_" internally so there is no behaviour change. This change is simple enough it could potentially be backported to older version of bitbake meaning layers using the new syntax/markup could work with older releases. Even if other no other changes are accepted at this time and we don't backport, it does set us on a path where at some point in future we could require a more explict syntax. I've tested this patch by converting oe-core/meta-yocto to the new syntax for overrides (9000+ changes) and then seeing that builds continue to work with this patch. (Bitbake rev: 0dbbb4547cb2570d2ce607e9a53459df3c0ac284) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* initscripts: make DISTRO_FEATURE safeBruce Ashfield2020-01-222-15/+17
| | | | | | | The initscripts bbappend should only activate when virtualization is in distro features. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* bbappend: switch to use a wildcard beyond major versionMark Asselstine2015-09-081-0/+0
| | | | | | | | | | | | Using a wildcard will simplify things when using meta-virtualization against different yocto or oe branches and prevent having to make future updates to keep in step with package uprevs. The changes found within these bbappend tend to be generic and non-version specific, thus safe for 'porting' via wildcard. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* initscripts: fix do_install_append rule.Paul Barrette2013-11-041-1/+1
| | | | | | | | | Fix commit ID: cafc94c4a2b599d553712dcbb1b01eefd1ef3941 The above commit missed a redirect for the final closing bracket. Signed-off-by: Paul Barrette <paul.barrette@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* initscripts: add warning and begin functions to lsb_log_messagePaul Barrette2013-10-291-0/+6
| | | | | | | | | | | Some init scripts call a "begin" or "warning" function to log early init phase messages, e.g. openvswitch-controller. These functions are not part of the default /etc/init.d/functions script, which is provided by oe-core's lsb pkg. Append these two missing commands to /etc/init.d/functions during the install phase. Signed-off-by: Paul Barrette <paul.barrette@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* initscripts: Remove .swp file accidentally committed.Raymond Danks2012-06-271-0/+0
| | | | Signed-off-by: Raymond Danks <ray.danks@se-eng.com>
* initscripts: xen initscripts utilize success and failure functions.Raymond Danks2012-06-212-0/+10
Signed-off-by: Raymond Danks <ray.danks@se-eng.com>