| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
Originally I was just trying to remove the reference to DEPLOY_DIR_IMAGE
because it depends on MACHINE, but then I realized that this recipe is
just plain not worth keeping. It isn't viable for anything except the
most limited testing, since it bakes device-specific credentials into an
image, but we weren't even using it for testing.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This is a bit of a compromise. These recipes are allarch, since they do
not depend on an architecture, but they depend on aktualizr, which is
definitely not allarch. Therefore, we must tell bitbake not to treat the
aktualizr architecture as a dependency of these recipes.
However, this means that if one of the config files changes in the
aktualizr repo, we need to bump the version of the recipe that uses it
to make sure bitbake picks up that change.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
| |
|
|
|
|
|
| |
Most do not need to depend on aktualizr-native and do not need to be
rebuilt if the credentials change.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|
|
"Autoprovisioning" or "automatic provisioning" is now known as "shared
credential provisioning". "Implicit provisioning" is now known as
"device credential provisioning". "HSM provisioning" was always a
misnomer, so it is now refered to as "device credential provisioning
with an HSM".
This includes a bump of the aktualizr version as well.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
