On Fri, Jul 11 2014, Daniel Kahn Gillmor <d...@fifthhorseman.net> wrote: > Perhaps more cleanly, it would be nice to have a way that modules can > add or remove packages to the initial bootstrap (via --include and > --exclude arguments to debootstrap), where the daemon start/stop are > already inhibited, so that we can reuse that mechanism instead of trying > to maintain our own separately in debirf? > > i'm not sure what format we'd use for that, since the current modules > format is pretty raw. And, on the other hand, it wouldn't cover > packages added by new mirrors or other repositories :/ > > jrollins, any preference on how to do this?
I like the idea of a mechanism by which modules could specify packages to be added via debootstrap. Maybe a special comment in the module that could be grep'd out? Maybe modules could have a comment like: # DEBIRF_PACKAGES=(package0 package1) or # DEBIRF_PACKAGES: package0 package1 If it's formatted like a variable I guess it doesn't necessarily need to be a comment, but it might be better to not have it be part of the module code itself. We could then build the additional install list with something like: prefix='# DEBIRF_PACKAGES: ' packages=($(grep -h "$prefix" "$DEBIRF_MODULES"/* | sed "s/^$prefix//")) We could also just specify a package list in a separate file, say $DEBIRF_MODULES/packages, one per line. jamie.
pgpTxUmdfGWRF.pgp
Description: PGP signature
