[Releasing] 5.0.0-rc2 build issues on Linux

[Mika Boström]

There are some odd build issues on Linux, when going piece-by-piece,
tarballs generated with git-archive. This happens at Mer-project, when
I'm trying to build qt5 in OBS. There are essential modules that can't
be built.

[Build monitor page]
https://build.pub.meego.com/projec/monitor?project=home%3Abostik%3AQt5a1


Modules failing to build at RC2:

                  Last tag
------------------------------
qt3d                beta1
qtimageformats      rc2   !!
qtquick1            rc2   !!
qtlocation          beta1  *
qtsensors           beta1
qtsystems           beta1
qtwayland           beta1

[*]: qtlocation depends on qt3d, so is not built at all

All modules above fail with identical error:
"Project ERROR: Project has no top-level .qmake.conf file"


In addition, QtWebKit and umbrella repo qt5.git do not have -rcX tags:

                  Last tag
------------------------------
qtwebkit            beta2
qt5.git             beta1


QtWebKit is designated an "essential" module. At the moment, it is
therefore not possible to build Qt5 release candidate(s) from git
directly. The SHA1 used is not available from the release tarball
either.

All the modules built nicely at -beta1, so the ".qmake.conf" error comes
from somethind done at a later date. There have been 79 commits in
qtbase/qmake/** since -beta1:

~/qt5/qtbase/qmake% git log --oneline v5.0.0-beta1..v5.0.0-rc2 . | wc -l
79

The git-generated tarball for qtquick1 _does_ contain a non-empty
.qmake.conf so the error message is just wrong.

Logically there must be some common reason for the build failures, but I
don't see what it could be.


-- 
 Mika Boström / mika.bostrom at nomovok.com
 Software Architect