Hi, currently config.sh creates several SoC specific files ad-hoc (i.e. using echo). This has several drawbacks:
- it bloats config.sh (e.g 840 lines for the omap beagle /var/lib/alsa/ asound.state) - it creates files which are not tracked by RPM - most importantly, these files are never updated All these files could be moved into some SoC specific package, e.g. soc- config-$(kiwi-iname). If there are no objections, I will prepare an appropriate package and submit to Factory. The next step then is to remove the config file creation from the JeOS files and Require the SoC specific package instead. The list of affected files (sorted by kiwi image name): arndale: /etc/dracut.conf.d/exynos_modules.conf [1] /etc/modprobe.d/90-blacklist-xhci.conf chromebook: /etc/dracut.conf.d/exynos_modules.conf [1] /etc/X11/xorg.conf.d/50-touchpad.conf /etc/modules-load.d/cros-ec-keyb.conf beagle: /etc/dracut.conf.d/omap_modules.conf /etc/modprobe.d/50-omapdrm.conf /var/lib/alsa/asound.state panda: /etc/dracut.conf.d/omap_modules.conf /etc/modprobe.d/50-omapdrm.conf beaglebone: /etc/dracut.conf.d/beagleboneblack_modules.conf pine64, cubietruck, cubieboard, olinuxino: /etc/dracut.conf.d/sunxi_modules.conf sabrelite: /etc/dracut.conf.d/sabrelite_modules.conf /etc/modules-load.d/imx6.conf raspberrypi: /etc/dracut.conf.d/raspberrypi_modules.conf [2] /etc/modprobe.d/90-blacklist-vc4.conf raspberrypi2: /etc/dracut.conf.d/raspberrypi_modules.conf [2] raspberrypi3: /etc/dracut.conf.d/raspberrypi_modules.conf [2] /etc/modprobe.d/50-rpi3.conf socfpgade0nanosoc: /etc/dracut.conf.d/socfpga_modules.conf odroidc2, nanopik2: /etc/dracut.conf.d/meson_gxbb_modules.conf m400: /etc/sysconfig/network/ifcfg-enp1s0 Kind regards, Stefan [1] contents of exynos_modules.conf for chromebook and arndale differs [2] contents of raspberrypi_modules.conf for rpi1/rpi2/rpi3 differs -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019
signature.asc
Description: This is a digitally signed message part.
