Overview
Request 795729 accepted
- base pattern cleanup:
* make minimal_base really minimal by moving packages to base instead. Only
pull in the release package and branding. So this is really what
can be used for application containers, portable services etc.
In it's current form it also pulls in bash, glibc, coreutils
etc, so no need to specify explicitly.
* strip down base so it forms a minimal booting system that can install
packages.
* don't pull in man into transactional system
What installs openSUSE-build-key, bash-completion and man now?
procps can be dropped here, zypper hard requires that now.
Dropping the suggests for openSUSE-release will break installs using the openstack disk image builder again...
I am a bit undecided about the build key packages TBH. They are basically useless currently. They don't install into %_keyringpath after all. So we always rely on something external to import the keys. They would be required again if we'd switch to %_keyringpath. There must be a feature somewhere that got declined years ago. Maybe worth revisiting if that's useful.
bash-completion and man are recommended by enhanced_base. I was hoping that is enough.
Where are those openstack disk images? Shouldn't they explicitly decide which product they want to be?
They're useless after the key got copied in the right place, yes. Whatever does the copying might rely on their presence in the system though... kiwi's suseImportBuildKey does, for instance.
Yep, but they currently don't. Might be as easy as adding it here though: https://github.com/openstack/diskimage-builder/blob/master/diskimage_builder/elements/opensuse-minimal/environment.d/10-opensuse-distro-name.bash#L4
suseImportBuildKey runs in config.sh right? So that is after installation. How does zypper know which packages to trust before?
Not sure. I assume it uses the host's trust during bootstrap.
kiwi logs are full of NOKEY warnings. I wonder why those are just warnings rather than errors.
Probably zypper checks the rpm itself instead of leaving that to rpm...
Ah, and wrt procps I think it makes sense to state it explicitly as we do want ps etc. I assume, even in case we remove zypper there ...
Technically we don't need it though, so if the system can boot to a shell which can be used to install it, it doesn't have to be hard required
Request History
lnussel created request
- base pattern cleanup:
* make minimal_base really minimal by moving packages to base instead. Only
pull in the release package and branding. So this is really what
can be used for application containers, portable services etc.
In it's current form it also pulls in bash, glibc, coreutils
etc, so no need to specify explicitly.
* strip down base so it forms a minimal booting system that can install
packages.
* don't pull in man into transactional system
lnussel accepted request
Added build-key back as per Fabians comments. May need sr#795732