On Thursday, 27.08.2015 at 11:23, Justin Cormack wrote: > On 27 August 2015 at 11:13, Wei Liu <[email protected]> wrote: > > > > Editing the configuration file works fine for me at the moment because I > > build everything including the toolchain. > > > > It's just not nice and might not work all the time -- considering > > rumpbake is going to be installed by packaging system and the default > > rumpbake.conf buried in some directories that user of the toolchain > > doesn't have permission to edit. > > Also right now it is a file that is in version control, so editing it > is annoying > when working with upstream. > > Being able to specify an alternate config file or put all the arguments on the > command line is much easier for automated builds.
In that case, I can do the following: 1. Add a '-c CONFIG' option to rumpbake. 2. Reserve (note in the source) the same '-c CONFIG' option to rumprun, so that we don't accidentally use it for something else and can be consistent with rumpbake later. 3. Additionally, search for a rumpbake.conf in some well-defined path, say $HOME/.config/rumpkernel.org/rumpbake.conf. Thoughts?
