5,576
edits
Changes
From SME Server
Jump to navigationJump to searchBuild an Official ISO (view source)
Revision as of 17:51, 31 December 2014
, 17:51, 31 December 2014→discussion on the Iso build
====discussion on the Iso build====
====discussion on the Iso build====
[[bugzilla:7675]]
[[bugzilla:7675]]
build_installer and build_ISO are meant to be run in a mock chroot with the stage tree nfs mounted into it. The build box can be the same, eg COS6 x64 for all ISOs, it is only the mock image that needs to match the ISO, and this is magically handled by the mock configs. You also need to have access to the extras repo as many of the packages needed to build the installer and ISO are contained in there. This repo is to house the needed packages that aren't going to be included in the ISO. For clarification read http://bugs.contribs.org/show_bug.cgi?id=7675#c37
build_installer and build_ISO are meant to be run in a mock chroot with the stage tree nfs mounted into it. Each installer and ISO needs to built on the corresponding version (cos5 for sme8 and cos6 for sme9). You also need to have access to the extras repo as many of the packages needed to build the installer and ISO are contained in there. This repo is to house the needed packages that aren't going to be included in the ISO.
The os, updates, and updates-testing repos are included so we can stage the packages we are going to release without actually having to release them. Normally the updates-testing repo is used for verification (testing is for developer testing). During the ISO release schedule (usually very short) I hold moving packages to updates-testing until I have the ISO built.
The os, updates, and updates-testing repos are included so we can stage the packages we are going to release without actually having to release them. Normally the updates-testing repo is used for verification (testing is for developer testing). During the ISO release schedule (usually very short) I hold moving packages to updates-testing until I have the ISO built.
