After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 683416 - bring back -a --autogen command-line option
bring back -a --autogen command-line option
Status: RESOLVED FIXED
Product: jhbuild
Classification: Infrastructure
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Jhbuild maintainers
Jhbuild QA
: 683496 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-09-05 12:49 UTC by Craig Keogh
Modified: 2012-09-28 12:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Craig Keogh 2012-09-05 12:49:28 UTC 
In a recent change, JHBuild only autogens if configure.ac is newer than configure (bug 660844). The -a --autogen options make sense again. Bring them back. -a --autogen were removed in [1].

[1] http://git.gnome.org/browse/jhbuild/commit/?id=96182ea661cc65c42afe6b11972230e6c1ffbb55
Comment 1 Bastien Nocera 2012-09-06 12:55:47 UTC 
After changing my ~/.jhbuildrc, I'm trying to rebuild totem-pl-parser with the --enable-code-coverage option.
jhbuild -afn buildone totem-pl-parser
will jump straight to installing it.

touch configure.ac
is a crappy work-around, IMO.
Comment 2 Craig Keogh 2012-09-06 13:08:04 UTC 
(In reply to comment #1)
> After changing my ~/.jhbuildrc, I'm trying to rebuild totem-pl-parser with the
> --enable-code-coverage option.
> jhbuild -afn buildone totem-pl-parser
> will jump straight to installing it.

Bug 683374 will help here too. JHBuild will detect changes to autogen arguments (like --enable-code-coverage) and then re-run autogen.sh.
Comment 3 Craig Keogh 2012-09-06 23:16:20 UTC 
*** Bug 683496 has been marked as a duplicate of this bug. ***
Comment 4 Bastien Nocera 2012-09-25 11:56:32 UTC 
This problem is seriously starting to annoy me. Now I need to go in the directory of the dependency I want to force build and execute multiple commands when one used to suffice.
Comment 5 Colin Walters 2012-09-25 13:44:20 UTC 
(In reply to comment #4)
> This problem is seriously starting to annoy me. Now I need to go in the
> directory of the dependency I want to force build and execute multiple commands
> when one used to suffice.

Isn't this fixed by bug 683374?
Comment 6 Craig Keogh 2012-09-25 23:37:15 UTC 
I think JHBuild should provide a -a option, but I am also interested to know why you need to force an autogen Bastien? Perhaps there is an underlying JHBuild bug?
Comment 7 Bastien Nocera 2012-09-26 09:18:16 UTC 
(In reply to comment #6)
> I think JHBuild should provide a -a option, but I am also interested to know
> why you need to force an autogen Bastien? Perhaps there is an underlying
> JHBuild bug?

Because I manually made changes to the environment (in this case, removed left-over libsoup bits in the tree), and I wanted to force autogen.sh to be run with the right arguments.

I also use -afn to get jhbuild to run autogen.sh for me for software that's not listed in jhbuild. I would git clone the repo, and run jhbuild -afn, which would run autogen.sh with the right arguments.
Comment 8 Bastien Nocera 2012-09-26 09:23:34 UTC 
And the bug is still current. The "-f" part of the options is a clear sign that I don't want jhbuild to try and be cleverer than me.