On 04/29/2014 09:38 PM, Simon McVittie wrote:
> I see there's a TODO in bootstrap-debootstrap for reading options from
> config/options/cdebootstrap. Is that the new UI for a user to do what
> used to be done via --debootstrap-options, or is the idea that lb config
> should create that file?
general disclaimer: you're using 4.x, which has many rough edges and
such, so.. i'm aware that there are lots of things to finish before its
properly usuable, and any help getting it done faster is more than welcome.
the general plan is this:
* lb init would do more-or-less what lb config did wrt/ initialize a
config tree in a previously empty directory.
* lb config would be a set/get program only
this means:
* if the user would do lb init, it would probably touch an empty
config/options/cdebootstrap
* if the user then wants to set cdebootstrap options, he could use
e.g.
lb config --set options.cdebootstrap "--exclude=package1,package2"
which would then write:
[cdebootstrap]
options = --exclude=package1,package2
into config/options/cdebootstrap
* lb bootstrap-cdebootstrap would then read (if existing)
options/config/cdebootstrap and use the options specified there
when invoking cdebootstrap.
hope that helps,
Daniel
--
Address: Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: daniel.baumann@progress-technologies.net
Internet: http://people.progress-technologies.net/~daniel.baumann/