On Fri, Jan 15, 2010 at 4:32 PM, Tong Sun <suntong001@gmail.com> wrote:

e.g. you set DEBOOTSTRAP_OPT in the config file, but it is
not used/executed. From my point of view a little bit problematic.

I'll take a look at it.

what do you mean by "not used/executed"?

$ grep -E 'DEBOOTSTRAP_OPT|_opt_debopt' *
cmdlineopts.clp:    shift; _opt_debopt="$1"
config:# DEBOOTSTRAP_OPT='--include=debconf-utils,locales,pciutils --exclude=nano,tasksel,tasksel-data,iptables'
grml-debootstrap:[ "$_opt_debopt" ]              && DEBOOTSTRAP_OPT=$_opt_debop
grml-debootstrap:     einfo "Running $DEBOOTSTRAP $DEBOOTSTRAP_OPT for release ${RELEASE}${ARCHINFO} using ${MIRROR}${ISO}"
grml-debootstrap:        $DEBOOTSTRAP $ARCHCMD $KEYRING $DEBOOTSTRAP_OPT $RELEASE $MNTPOINT $MIRROR
grml-debootstrap:        $DEBOOTSTRAP $ARCHCMD $KEYRING $DEBOOTSTRAP_OPT $RELEASE $MNTPOINT $ISO

It get set in cmdlineopts.clp, and get passed all the way to $DEBOOTSTRAP. Any questions?

ps,

I still think --packages or --debconf without the optional parameters is useful. It normally takes me more than 3 iterations to use grml-debootstrap, not every time I need to install extra packages and pre-seed packages. I believe such request is not uncommon.

pps,

I was talking about --debconf, not--debopt

cheers