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.
all developers can force a build by doing an svn commit to the src/build/CD-administrator directory
how to exclude packages from the cd
Get the curret status
grab CD-administrator with svn co svn+ssh://$firstname.lastname@example.org/svn/debian-edu/trunk/src/build/CD-administrator
- cd CD-administrator
patch using ./patch-debian-cd
edit the patch
edit the exlude file with vi debian-cd/tasks/exclude-etch
regenerate the patch with ./make-patch
Test that your patch works with ./patch-debian-cd
commit your changes to the patchfile with svn commit debian-cd.patch
- have a beer and wait for the cd to build
famous last words
... and any technology distinguishable from magic is not sufficiently advanced!