http://bugzilla.opensuse.org/show_bug.cgi?id=1091804 http://bugzilla.opensuse.org/show_bug.cgi?id=1091804#c5 --- Comment #5 from Fabian Vogt <fvogt@suse.com> --- (In reply to Jean-Philippe Evrard from comment #4)
(In reply to Fabian Vogt from comment #3)
(In reply to Alexander Graf from comment #2)
We even have them for x86_64 already: https://build.opensuse.org/package/view_file/openSUSE:Factory:ARM:Live/JeOS/ X11-rootfs.x86_64.kiwi?expand=1
I guess it makes sense to consolidate our images into something more managable for everyone, yes.
I guess for this we should actually start from scratch and just make a new package/.kiwi file which includes all packages necessary to run zypper and is arch-independant. It would also avoid kiwi profiles, which makes it even easier to maintain.
Opinions?
I am new to all of this, so just my two cents:
I guess it could be simplified from https://build.opensuse.org/package/view_file/openSUSE:Factory:ARM:Live/JeOS/ JeOS-efi.x86_64.kiwi?expand=1 .
I like the idea of having a minimum base arch-independant and adding layers.
The images itself are not arch independent, just the image descriptions would be. The descriptions for bootable images can't be as the image types and boot flows differ.
It could become technically challenging if there are other extra (distro-specific) packages required for a "minimum bootable image". But all in all, it's a step towards the right direction to avoid the repetitions. It would require rebuilding all the other images, and check for regressions. I am not sure the state of the testing there, and if there are resources to work on it.
IMO we only need one type of rootfs, "one size fits all". It just needs to contain zypper and all dependencies. Additional requirements are that it does not break dependencies or modifies any config files unexpectedly. -- You are receiving this mail because: You are on the CC list for the bug.