Skip to content

GitLab

Switch branch/tag
  1. 17 Feb, 2023 1 commit
  3. 02 Aug, 2021 1 commit
    • Bruce Ashfield's avatar
      global: overrides syntax conversion · d876cfc5
      Bruce Ashfield authored 
      
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: default avatarRichard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: default avatarBruce Ashfield <bruce.ashfield@gmail.com>
      d876cfc5
  5. 04 Jun, 2021 1 commit
  7. 09 Feb, 2021 1 commit
  9. 06 Feb, 2021 1 commit
  11. 27 Feb, 2020 1 commit
  13. 10 Dec, 2019 1 commit
  15. 22 Nov, 2019 1 commit
  17. 12 Jul, 2019 1 commit
    • Bruce Ashfield's avatar
      cri-o: update to 1.15 · 7525f301
      Bruce Ashfield authored 
      
Updating to the 1.15 release.

With this update there are significant new build constraints and
dependencies. As such, the cross binaries are now being be built
by default, with the old (non-cross) build being kept around as
an optional way to build the components.

There are still issues with the non-cross build, so it will
require more work in the future.

We also document the requirement for selinux and seccomp in the
README as dependencies if you build cri-o.
Signed-off-by: default avatarBruce Ashfield <bruce.ashfield@gmail.com>
      7525f301
  19. 04 Dec, 2018 1 commit
  21. 24 May, 2018 1 commit
  23. 22 Mar, 2018 1 commit
  25. 14 Mar, 2018 1 commit
  27. 15 Nov, 2017 1 commit
  29. 22 Oct, 2017 1 commit
  31. 02 Oct, 2017 1 commit
  33. 19 Dec, 2016 1 commit
  35. 10 Aug, 2015 1 commit
  37. 06 Aug, 2015 1 commit
  39. 29 Jul, 2015 1 commit
  41. 31 Mar, 2015 1 commit
  43. 01 Dec, 2014 1 commit
  45. 09 Jul, 2014 1 commit
  47. 18 Oct, 2013 1 commit
  49. 18 Jan, 2013 1 commit
  51. 20 Dec, 2012 1 commit
  53. 07 Dec, 2012 2 commits
  55. 30 Nov, 2012 1 commit
  57. 22 Jun, 2012 1 commit
  59. 21 Jun, 2012 1 commit