meta/conf/layers.conf: Add ca-certificates as ABISAFE
PATCH 1/2 meta/conf/layers.conf: Add ca-certificates as ABISAFE
meta-oe was doing this before, but it was triggering a yocto-compat-script failure during the signature checking.
The ca-certificates changing is ABISAFE, as the certificates themselves do not modify the compiles behavior of the applications. This should permit easier upgrades without as much rebuilding.
The original value was set in meta-oe by commitff7a4b13c4efeffc5853a93c6ff7265fa3d6c143.
--- meta/conf/layer.conf | 1 + 1 file changed, 1 insertion(+)
meta/conf/layer.conf +1 -0
@@ -40,6 +40,7 @@ SIGGEN_EXCLUDERECIPES_ABISAFE += " \ base-passwd \ opkg-utils \ gstreamer1.0-meta-base \ + ca-certificates \ " SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += " \
Signature · 1 line
1.8.3.1
PATCH 2/2 bitbake.conf: Add default FILESYSTEM_PERMS_TABLES
If FILESYSTEM_PERMS_TABLES was not defined, the default was selected by the packages.bbclass. This made it difficult for a recipe or layer to 'append' to the default.
Copy the default into the bitbake.conf, allowing future _append and += style actions.
--- meta/conf/bitbake.conf | 4 ++++ 1 file changed, 4 insertions(+)
meta/conf/bitbake.conf +4 -0
@@ -330,6 +330,10 @@ FILE_DIRNAME = "${@os.path.dirname(d.getVar('FILE', False))}" # This default was only used for checking FILESEXTRAPATHS ?= "__default:" +# Following is a duplication of the default defined in packages.bbclass, +# both should be kept in sync +FILESYSTEM_PERMS_TABLES ?= "${@'files/fs-perms.txt' if oe.types.boolean(d.getVar('VOLATILE_LOG_DIR', True)) else 'files/fs-perms-persistent-log.txt'}" + ################################################################## # General work and output directories for the build system. ##################################################################
Signature · 1 line
1.8.3.1
Re: [PATCH 2/2] bitbake.conf: Add default FILESYSTEM_PERMS_TABLES
Quoted 8 lines · Mark Hatle
If
FILESYSTEM_PERMS_TABLESwas not defined, the default was selected by the packages.bbclass. This made it difficult for a recipe or layer to 'append' to the default.Copy the default into the bitbake.conf, allowing future
_appendand += style actions.Signed-off-by Mark Hatle <[email protected]>
Couldn't package.bbclass one to be dropped?
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Re: [PATCH 2/2] bitbake.conf: Add default FILESYSTEM_PERMS_TABLES
Quoted 5 lines · Otavio Salvador
Quoted 4 lines · Mark Hatle
If
FILESYSTEM_PERMS_TABLESwas not defined, the default was selected by the packages.bbclass. This made it difficult for a recipe or layer to 'append' to the default.
Quoted 8 lines
Quoted 4 lines
Copy the default into the bitbake.conf, allowing future
_appendand += style actions.Signed-off-by Mark Hatle <[email protected]>Couldn't package.bbclass one to be dropped?
Yes, I didn't do it at present because I was worried it could affect someone and it's after feature freeze.
If RP is not concerned about this, I can create a V2 that also removes the piece of package.bbclass.
--Mark
Re: [PATCH 2/2] bitbake.conf: Add default FILESYSTEM_PERMS_TABLES
Quoted 7 lines · Mark Hatle
Quoted 6 lines · Otavio Salvador
On Wed, Sep 13, 2017 at 12:15 PM, Mark Hatle <mark.hatle@windriver.
Couldn't package.bbclass one to be dropped?
Quoted 7 lines
Yes, I didn't do it at present because I was worried it could affect someone and
it's after feature freeze.If RP is not concerned about this, I can create a V2 that also removes the piece
of package.bbclass.
I'm ok with this.
Cheers,
Richard