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 697875 - [PATCH] autogen.sh: Add a hack to work in the gnome-ostree build system
[PATCH] autogen.sh: Add a hack to work in the gnome-ostree build system
Status: RESOLVED FIXED
Product: jhbuild
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Jhbuild maintainers
Jhbuild QA
Depends on:
Blocks:
 
 
Reported: 2013-04-12 13:38 UTC by Colin Walters
Modified: 2013-09-17 11:44 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
0001-autogen.sh-Add-a-hack-to-work-in-the-gnome-ostree-bu.patch (1.44 KB, patch)
2013-04-12 13:38 UTC, Colin Walters 		committed Details | Review

Description Colin Walters 2013-04-12 13:38:10 UTC 
gnome-ostree doesn't support passing parameters to autogen.sh, but
we can't do the full autotools thing because we don't have yelp.

A simple hackaround for this is to check NOCONFIGURE; if someone's
specifying that we just give them the autotools always.
---
Comment 1 Colin Walters 2013-04-12 13:38:39 UTC 
Created attachment 241347 [details] [review]
0001-autogen.sh-Add-a-hack-to-work-in-the-gnome-ostree-bu.patch
Comment 2 Frederic Peters 2013-08-16 13:19:33 UTC 
Comment on attachment 241347 [details] [review]
0001-autogen.sh-Add-a-hack-to-work-in-the-gnome-ostree-bu.patch

Reviewed so I can improve my bugzilla score. Yeah.
Comment 3 Germán Poo-Caamaño 2013-09-07 22:29:16 UTC 
This is related with https://bugzilla.gnome.org/show_bug.cgi?id=706497

Not sure whether it is a duplicated or not.
Comment 4 David King 2013-09-17 11:44:14 UTC 
Comment on attachment 241347 [details] [review]
0001-autogen.sh-Add-a-hack-to-work-in-the-gnome-ostree-bu.patch

This was committed as ea9c867401e04f2537901e8ec09d7be26d2c6c6e. As Germán pointed out, this caused bug 706497, and there are a couple of patches to fix the problem attached to that bug.