[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

preparing for a new simple-cdd release

i am very happy to annouce that a version of simple-cdd that works with
etch is nearly finished.  i've tested it using debian-installe RC1, and
it seems to be working fine.


many thanks to Gustavo Franco (a.k.a. stratus) for doing much of the
work to get simple-cdd back in shape. thanks also to Frans Pop for help
troubleshooting debian-installer issues.

hopefully, with a little more testing, we will see an upload to debian

the major new change (since the sarge-oriented version) is that it uses
a .udeb to integrate into debian-installer.  this udeb is simply a
skeletal infrastructure for a CDD to select packages for installation,
do debconf preseeding/preconfiguration, and run custom post-install
scripts. you can define several profiles, with different
package/preseeding/post-install sets and select them at install time.

feedback would definitely be appreciated. if you want to give it a try,
on an etch system:

apt-get install bzr rsync debian-cd reprepro apt-utils wget debhelper cdbs libdebian-installer4-dev libdebconfclient0-dev 

bzr get http://cdd.alioth.debian.org/bzr/simple-cdd/etch-simple-cdd

cd etch-simple-cdd

create a profile named NAME:

echo list of packages you want installed > profiles/NAME.packages

for debconf preseeding, put a debconf-set-selections compatible file
into profiles/NAME.preseed

for a custom post-install script, place it in profiles/NAME.postinst

debuild -us -uc -I.bzr -b (to build the .udeb)

./build-simple-cdd --profiles NAME --local-packages ../simple-cdd-profiles_0.3.0~1_all.udeb

this will create a partial package mirror in the dir "mirror", and if
all goes well, an .iso file in the "images" dir.

(alternately, use ./qemu-test instead of ./build-simple-cdd, which will
call build-simple-cdd and attempt to boot the CD with qemu)

try "./build-simple-cdd --help" for more options

there's a few changes i'd like to finish soon, mentioned in the TODO

live well,

Reply to: