|Deletions are marked like this.||Additions are marked like this.|
|Line 9:||Line 9:|
|* missingpkglist is generated by comparing the list of packages on the CD with the list of wanted packages.|
|Line 18:||Line 19:|
|= cd-build logs =|
|Line 19:||Line 21:|
|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.|
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.
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.
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.
famous last words
... and any technology distinguishable from magic is not sufficiently advanced!