linux/meta-updater.git/conf, branch feat/headersMirror of github.com/advancedtelematic/meta-updaterhttps://git.enea.com/cgit/linux/meta-updater.git/atom?h=feat%2Fheaders2020-08-03T11:47:30+00:00Inherit python3native instead of using HOSTTOOLS.2020-08-03T11:47:30+00:00Patrick Vacekpatrickvacek@gmail.com2020-08-03T06:58:53+00:00urn:sha1:628c4e317618d1b03da41e43cf0ede69c1fa4695
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
meta: change virtual/network-configuration to network-configuration2020-05-10T08:36:20+00:00Ming Liuming.liu@toradex.com2020-05-10T08:36:20+00:00urn:sha1:5e08158e9eae225ce74017f5ea51fdf1ba27943b
The name 'virtual' is a recipe specific concept but not a package
specific one, it's confusing that a package provides 'virtual/' names.
Let's drop 'virtual/' from network-configuration, to keep consistent
with yocto naming styles.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
layer.conf: update LAYERSERIES_COMPAT for dunfell2020-03-25T13:06:48+00:00Martin JansaMartin.Jansa@gmail.com2020-03-25T13:06:48+00:00urn:sha1:92ab3bbf186d93736c36b35c22ecb86d72f944d7
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
meta: move HOSTTOOLS definitions to sota.conf.inc2020-01-30T15:07:07+00:00Ming Liuliu.ming50@gmail.com2020-01-26T21:14:20+00:00urn:sha1:3a2fecfc1d78e4b161f7180f35fc7d0a1a967ae6
HOSTTOOLS and HOSTTOOLS_NONFATAL are global variables that being
handled in base_eventhandler, so they must be defined in config files
or in INHERIT classes or classes being inherited by base.bbclass, or
else we might run into the following problems:
```
$ bitbake pkgname
$ bitbake imgname
```
the HOSTTOOLS and HOSTTOOLS_NONFATAL in the above image recipe, for
instance, 'repo python' in image_repo_manifest.bbclass, they would not
be copied to HOSTTOOLS_DIR.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
build and run image without ostree support for qemux86-642020-01-20T21:00:41+00:00Kostiantyn Bushkokbushko@intellias.com2020-01-17T11:37:14+00:00urn:sha1:ad01ab114dd83edda61c06aa01fd899c80ee0a68
Signed-off-by: Kostiantyn Bushko <kbushko@intellias.com>
Force a simple reproducible build mechanism2019-12-04T10:46:30+00:00Laurent Bonnanslaurent.bonnans@here.com2019-12-04T10:39:58+00:00urn:sha1:af1694c7044aee54761750080819d5c5d6ce09e4
In 25a17f0346ab05b3212bb280e4a8b622bcf99bce, poky sets
reproducible_build by defaults. However, it is quite complex as it tries
to compute a plausible timestamp from source files, in a reproducible
ways.
Setting the timestamps to 0, just like ostree, is probably safer in our
case, so let's switch to our old behavior.
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
OTA-3988: Split the local.conf to a base and a distro specific part2019-11-06T12:35:34+00:00Mykhaylo Sulext-mykhaylo.sul@here.com2019-11-06T08:44:03+00:00urn:sha1:c74c4eb5399ed7a195e00172774a283582da6e44
Signed-off-by: Mykhaylo Sul <ext-mykhaylo.sul@here.com>
OTA-3988: make the DISTRO value in poky-sota-systemd.conf aligned to the systemd case2019-11-05T16:35:43+00:00Mykhaylo Sulext-mykhaylo.sul@here.com2019-11-05T16:35:43+00:00urn:sha1:3f904325ad5d307f308e020e9bc4d24a8afdf7af
Signed-off-by: Mykhaylo Sul <ext-mykhaylo.sul@here.com>
OTA-3988: force an ostree boot indication only in case of non-systemd distro2019-11-05T09:09:25+00:00Mykhaylo Sulext-mykhaylo.sul@here.com2019-11-05T08:17:53+00:00urn:sha1:40153ba5d77a83e78a9b844a8117b44be8b55df0
Signed-off-by: Mykhaylo Sul <ext-mykhaylo.sul@here.com>
OTA-3988: Non-systemd/poky-sota local.conf2019-11-01T10:02:30+00:00Mykhaylo Sulext-mykhaylo.sul@here.com2019-11-01T10:02:30+00:00urn:sha1:6680bfb70ce2285ef5243e489073fb26bc63f0e7
Signed-off-by: Mykhaylo Sul <ext-mykhaylo.sul@here.com>