[opensuse-factory] Kiwi restart
Hi, this question could not really be answered in o-support@o.o (in special the part about current live-images), I try here: As SUSE Studio is faded away already some time, I want to make a new attempt in image-building. Needless to say, the old sources dont work, and the documentation e.g. on https://en.opensuse.org/Portal:KIWI is close to its 10 years anniversary of not being touched. Taking a look at https://build.opensuse.org/project/show/openSUSE:Factory:Live I would like to understand how currently the live images are build. I looks like there is an additional script that puts pieces like list- installer.sh, list-common.sh and list-kde.sh together to come up with a livecd-tumbleweed-kde.kiwi Can anyone explain? So, apparently the *kiwi is the place to start for a custom image, if one does not want to keep it generic? Thanks in advance Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----Original Message----- From: Axel Braun <axel.braun@gmx.de> Sent: 21 July 2020 12:22 To: opensuse-factory@opensuse.org Subject: [opensuse-factory] Kiwi restart
Hi,
this question could not really be answered in o-support@o.o (in special the part about current live-images), I try here:
As SUSE Studio is faded away already some time, I want to make a new attempt in image-building. Needless to say, the old sources dont work, and the documentation e.g. on https://en.opensuse.org/Portal:KIWI is close to its 10 years anniversary of not being touched.
You should probably have a look at the official documentation at https://osinside.github.io/kiwi/ I guess the wiki should point to this doc instead. Cheers, Guillaume
Taking a look at https://build.opensuse.org/project/show/openSUSE:Factory:Live I would like to understand how currently the live images are build.
I looks like there is an additional script that puts pieces like list- installer.sh, list- common.sh and list-kde.sh together to come up with a livecd-tumbleweed- kde.kiwi
Can anyone explain?
So, apparently the *kiwi is the place to start for a custom image, if one does not want to keep it generic?
Thanks in advance Axel
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, Am Dienstag, 21. Juli 2020, 12:21:44 CEST schrieb Axel Braun:
Hi,
this question could not really be answered in o-support@o.o (in special the part about current live-images), I try here:
As SUSE Studio is faded away already some time, I want to make a new attempt in image-building. Needless to say, the old sources dont work, and the documentation e.g. on https://en.opensuse.org/Portal:KIWI is close to its 10 years anniversary of not being touched.
Taking a look at https://build.opensuse.org/project/show/openSUSE:Factory:Live I would like to understand how currently the live images are build.
I looks like there is an additional script that puts pieces like list- installer.sh, list-common.sh and list-kde.sh together to come up with a livecd-tumbleweed-kde.kiwi
Can anyone explain?
Sure - that's pre-checkin.sh. Some time ago the TW live cds were built in a different way: 1. A bot generated a package list, which ends up as Requires: in a .spec file 2. This got pulled in by another .spec file, which was built as root and called kiwi to install that package list inside The .spec file from step 2 was even manually generated... This can be seen here: https://build.opensuse.org/project/show/openSUSE:13.2:Live Now it's just one step of file generation with pre-checkin.sh, which only has to be run manually after changes to the list-*.sh files and there are no magic bots running.
So, apparently the *kiwi is the place to start for a custom image, if one does not want to keep it generic?
The package list in livecd-openSUSE is split over multiple .sh files to avoid duplication and writing xml manually. Especially the "buildignore" mechanism for ignoring recommended packages would be annoying otherwise. It also allows to keep the same source for TW and Leap. You can have it much simpler if you have a fixed list of packages to include and don't need to install recommended packages. Then you can just have a single .kiwi file with the right settings and packages. The kiwi documentation which was already linked can help there. Cheers, Fabian
Thanks in advance Axel
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello Guillaume and Fabian, Am Dienstag, 21. Juli 2020, 16:04:54 CEST schrieb Fabian Vogt: [...]
I looks like there is an additional script that puts pieces like list- installer.sh, list-common.sh and list-kde.sh together to come up with a livecd-tumbleweed-kde.kiwi
Can anyone explain?
Sure - that's pre-checkin.sh.
[...] thanks for this helpful input! Will dive in furhter! Best Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Axel Braun -
Fabian Vogt -
Guillaume Gardet