From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Henning Schild <henning.schild@siemens.com>
Subject: Expand DISTRO_APT_PREMIRROS syntax vs. install-only apt-sources
Date: Wed, 8 Jun 2022 09:18:23 +0200 [thread overview]
Message-ID: <9f0f5679-d79f-338f-c0f1-16071236482a@siemens.com> (raw)
Hi all,
we have more and more scenarios where local repos are used for the build
that require credentials to access them. Those URLs should not stay on
the devices images (nor should they show up in logs).
One idea to perform the required switch / purge after completing the
installation was to use DISTRO_APT_PREMIRRORS. It would help in some
scenarios but it also lacks some features:
- missing way to inject repo options (such as [check-valid-until=no]
when installing from a snapshot)
- no way to replace also the suite or components (yeah, actually a
limitation of the involved apt mirror, but that's life)
Now I'm wondering if we should either expand DISTRO_APT_PREMIRRORS to
cover those cases as well, or invent a different self-cleaning repo
switching mechanism. I'm already seeing brute-force repo purging classes
being written, but those do not fully cut it either if you want a work
apt configuration on the device.
Thoughts?
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
reply other threads:[~2022-06-08 7:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9f0f5679-d79f-338f-c0f1-16071236482a@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@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