<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY>
On Thu, 2010-11-25 at 14:51 -0800, Dan Nicholson wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#1a1a1a">jhbuild is designed primarily to operate with development checkouts,</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">and thus usually runs autogen.sh. It's operating on the assumption</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">that you might update your checkout and need to regenerate the</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">autotools. It's just a bug in the jhbuild code that it doesn't prefer</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">configure for tarballs. I looked at it and it seems that the</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">information to know that the source directory came from a tarball is</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">not available when it comes time to determine which script to run.</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">Probably need to open a bug on gnome.org.</FONT></TT><BR>
<BR>
</BLOCKQUOTE>
Actually what jhbuild does make sense. They are relying on the presence/absence<BR>
of this script to support both git/tarball builds. This is a widely adopted convention.
</BODY>
</HTML>