Hi, Quoting Benjamin Drung (2019-10-18 18:24:53) > I like to use mmdebstrap to produce a golden live image. This includes > calling several custom hooks. My current command line call for the > proof-of-concept is already more than 1000 characters long. That makes > memorizing the full command infeasible and I have to place the command > call into a shell script. > > It would be nice if the parameters for mmdebstrap could be placed into a > YAML configuration file so that running > `mmdebstrap --config=example.yaml` is enough to produce the output. > > Inspiration can be taken from > https://salsa.debian.org/raspi-team/image-specs/blob/master/raspi3.yaml > > What do you think about that idea? Do you like it or do you have an > alternative suggestion?
I'm not against this idea. Right now indeed the best option is to use a shell script instead of a configuration file. In both cases you end up having a file lying around somewhere and I didn't yet see sufficient advantage of making that file a configuration file instead of a shell script. Maybe you can convince me about the advantages of a configuration file over a shell script? Disadvantages are, that one has to learn yet another invented configuration file structure and/or format and that this will again increase the amount of necessary documentation, introduce new bugs and make an already complex piece of software even more complex and hard to understand. Thanks! cheers, josch
signature.asc
Description: signature