From: "Andreas J. Reichel" <andreas.reichel.ext@siemens.com>
To: isar-users@googlegroups.com
Cc: Andreas Reichel <andreas.reichel.ext@siemens.com>
Subject: [RFC v1 0/3] Fix additional apt repos with foreign keys
Date: Tue, 26 Feb 2019 14:48:41 +0100 [thread overview]
Message-ID: <20190226134844.8632-1-andreas.reichel.ext@siemens.com> (raw)
From: Andreas Reichel <andreas.reichel.ext@siemens.com>
This patch series fixes problems when adding a additional repos
which need different gpg keys for authentication.
The patches are designed to make the existing 'API', i.e. bitbake
variables work, not to solve the remaining design problems.
On basis of this series, we should discuss how to further proceed
since there should be a destinction wether we change the bootstrapping
apt source or if we change the apt source for additional packages.
If we change the bootstrapping apt source, we already need keys
installed in the build environment to do the first debootstrap.
If we only want additional packages in the target rootfs, we only
need to add keys inside the target chroot.
Currently this is not possible and requires additional bitbake
variables, i.e. APT_KEYS_TARGET_PKGS, or APT_KEYS_TARGET_BOOTSTRAP.
Also the reason for the option I delete in patch 3 is unclear to me.
This way we could never add additional repositories.
Andreas Reichel (3):
Fix path to user gpg-keys
Refactor gpg code to use apt code
Use all source lists in target root apt
meta/classes/isar-bootstrap-helper.bbclass | 14 ++++++++----
.../isar-bootstrap/isar-bootstrap.inc | 22 +++++++++----------
2 files changed, 21 insertions(+), 15 deletions(-)
--
2.20.1
next reply other threads:[~2019-02-26 13:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 13:48 Andreas J. Reichel [this message]
2019-02-26 13:48 ` [RFC v1 1/3] Fix path to user gpg-keys Andreas J. Reichel
2019-02-26 15:33 ` Henning Schild
2019-02-26 13:48 ` [RFC v1 2/3] Refactor gpg code to use apt code Andreas J. Reichel
2019-02-26 14:07 ` cedric_hombourger
2019-02-26 15:57 ` Henning Schild
2019-02-26 15:39 ` Henning Schild
2019-02-26 13:48 ` [RFC v1 3/3] Use all source lists in target root apt Andreas J. Reichel
2019-02-26 15:06 ` [RFC v1 0/3] Fix additional apt repos with foreign keys Henning Schild
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190226134844.8632-1-andreas.reichel.ext@siemens.com \
--to=andreas.reichel.ext@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox