Although this is not the most error-proof way to ensure an installation was successfully finished, this is already something that we can use to (try to) check whether the system was installed in an automated manner. Or, in other words, take those patches as the first step to be able to try to have some kind of CI around the unattended installations. This series does *not* touch Windows related stuff, but the plan is to also have the same done for Windows at some point in the future. Fabiano Fidêncio (6): install-script,debian: Add osinfo-install-successful file install-script,fedora: Add osinfo-install-successful file install-script,silverblue: Add osinfo-install-successful file install-script,opensuse: Add osinfo-install-successful file install-script,rhel,centos: Add osinfo-install-successful file install-script,ubuntu: Add osinfo-install-successful file data/install-script/debian.org/debian-preseed-desktop.xml.in | 4 ++++ data/install-script/debian.org/debian-preseed-jeos.xml.in | 4 ++++ .../fedoraproject.org/fedora-kickstart-desktop.xml.in | 3 +++ .../fedoraproject.org/fedora-kickstart-jeos.xml.in | 5 +++++ .../fedoraproject.org/silverblue-kickstart-desktop.xml.in | 3 +++ .../opensuse.org/opensuse-autoyast-desktop.xml.in | 3 +++ .../opensuse.org/opensuse-autoyast-jeos.xml.in | 3 +++ data/install-script/redhat.com/rhel-kickstart-desktop.xml.in | 3 +++ data/install-script/redhat.com/rhel-kickstart-jeos.xml.in | 5 +++++ data/install-script/ubuntu.com/ubuntu-preseed-desktop.xml.in | 4 ++++ data/install-script/ubuntu.com/ubuntu-preseed-jeos.xml.in | 4 ++++ 11 files changed, 41 insertions(+) -- 2.21.0 _______________________________________________ Libosinfo mailing list Libosinfo@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libosinfo
