debian-forge-composer/internal/blueprint/ext4_output.go
Lars Karlitski fe46fd3a89 blueprint: move ext4-filesystem towards lorax parity
The main difference (according to image-info) is an additional package
containing a gpg key which was used to verify packages. The one
generated by lorax-composer doesn't have this, because it doesn't verify
signatures.
2019-10-29 16:01:37 +01:00

34 lines
749 B
Go

package blueprint
import "github.com/osbuild/osbuild-composer/internal/pipeline"
type ext4Output struct{}
func (t *ext4Output) translate(b *Blueprint) *pipeline.Pipeline {
packages := [...]string{
"policycoreutils",
"selinux-policy-targeted",
"kernel",
"firewalld",
"chrony",
"langpacks-en",
}
excludedPackages := [...]string{
"dracut-config-rescue",
}
p := getCustomF30PackageSet(packages[:], excludedPackages[:])
addF30LocaleStage(p)
addF30GRUB2Stage(p, b.getKernelCustomization())
addF30FixBlsStage(p)
addF30SELinuxStage(p)
addF30RawFSAssembler(p, t.getName())
return p
}
func (t *ext4Output) getName() string {
return "filesystem.img"
}
func (t *ext4Output) getMime() string {
return "application/octet-stream"
}