GNOME Bugzilla – Bug 368820
Should reload jhbuildrc after configure failure
Last modified: 2009-05-03 12:39:32 UTC
When i got a error during ./configure stage, i often edit my ~/.jhbuildrc to modify some configure flags and try to fix the problem. After i ask to jhbuild to rerun configure stage (first option) but the ~/.jhbuildrc is not reloaded and so my modifications are ignored.
Confirming this. That's quite annoying. Currently, we need to tell people to edit the file, Ctrl+C the build, then rerun jhbuild buid --start-at=themodule which could be avoided.
The thing is reloading jhbuildrc is not enough but for the really simple things; common cases such as changing autogenargs also requires all the modules to be reloaded, which is far from simple.
After some refactoring of the different module types and version control systems to directly access the configuration object, here comes the patch that adds a new "[5] reload configuration" option to the terminal frontend. commit 393f51faff525581fdaea3b2da3a7ebcda803b71 Author: Frederic Peters <fpeters@0d.be> Date: Sun May 3 14:34:16 2009 +0200 [terminal] add option to reload configuration New option in terminal mode to let the user reload the configuration file without aborting JHBuild. (GNOME #368820) jhbuild/frontends/terminal.py | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-)