Differences between revisions 1 and 11 (spanning 10 versions)
Revision 1 as of 2006-10-14 18:09:13
Size: 443
Editor: HolgerLevsen
Comment:
Revision 11 as of 2007-03-07 16:05:03
Size: 1379
Editor: HolgerLevsen
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
This is in the very early stage of something whichad should become a howto to understand the build-process of the debia-edu (install) cd - please help to improve it. I will do so too, on my way to eternal wisdom and happyness :-) This is in the very early stage of something which should become a howto to understand the build process of the Debian Edu (install) cd - please help to improve it. I will do so too, on my way to eternal wisdom and happyness :-)
Line 6: Line 6:
tasks comes from debian-edu svn
wantedpkglist*.txt is generated from tasks
wantedpkglist is given to debian-cd to populate the cd
 * tasks comes from debian-edu svn
 * wantedpkglist*.txt is generated from tasks
 * wantedpkglist is given to debian-cd to populate the cd
 * missingpkglist is generated by comparing the list of packages on the CD with the list of wanted packages.

= debian-cd =

the code for the version of debian-cd we're using is at /home/builder/src/debian-edu/src/build/CD-administrator/debian-cd

During every build it's patched by debian-edu/src/build/CD-administrator/patch-debian-cd with debian-edu/src/build/CD-administrator/debian-cd.patch

If you want to exclude certain packages from the cd, there is a exclude-etch list (also used for etch-test) in that patch.

= cd-build logs =

the logs from each cd build are commited to svn (debian-edu/html/logs/cd-build-$suite.log). the commits are silent, so no commit-mail is sent.

= force re-build =

on a.skolelinux.no in .../src/build/CD-administrator/ do touch force-$SUITE to force a rebuild


= famous last words =

... and any technology distinguishable from magic is not sufficiently advanced!

Any sufficiently advanced technology is indistinguishable from magic...

This is in the very early stage of something which should become a howto to understand the build process of the Debian Edu (install) cd - please help to improve it. I will do so too, on my way to eternal wisdom and happyness :-)

  • tasks comes from debian-edu svn
  • wantedpkglist*.txt is generated from tasks
  • wantedpkglist is given to debian-cd to populate the cd
  • missingpkglist is generated by comparing the list of packages on the CD with the list of wanted packages.

debian-cd

the code for the version of debian-cd we're using is at /home/builder/src/debian-edu/src/build/CD-administrator/debian-cd

During every build it's patched by debian-edu/src/build/CD-administrator/patch-debian-cd with debian-edu/src/build/CD-administrator/debian-cd.patch

If you want to exclude certain packages from the cd, there is a exclude-etch list (also used for etch-test) in that patch.

cd-build logs

the logs from each cd build are commited to svn (debian-edu/html/logs/cd-build-$suite.log). the commits are silent, so no commit-mail is sent.

force re-build

on a.skolelinux.no in .../src/build/CD-administrator/ do touch force-$SUITE to force a rebuild

famous last words

... and any technology distinguishable from magic is not sufficiently advanced!