apparent circular build dependencies
The source package qttools-opensource-src has libqt5opengl5-dev as a
build dependency.
https://packages.ubuntu.com/source/bionic/qttools-opensource-src
libqt5opengl5-dev is provided by the source package
qtbase-opensource-src
https://packages.ubuntu.com/bionic/libqt5opengl5-dev
The source package qtbase-opensource-src has qttools5-dev-tools as a
build dependency.
https://packages.ubuntu.com/source/bionic/qtbase-opensource-src
qttools5-dev-tools is provided by the source package
qttools-opensource-src
So qttools-opensource-src can't be built without first building
qtbase-opensource-src and installing libqt5opengl5-dev, but
qtbase-opensource-src can't be built without first building
qttools-opensource-src and installing qttools5-dev-tools?
This would make it impossible to build either source package, so I must
be misunderstanding something. Can anyone clarify?
What's Bionic based on - Jessie? Stretch? Might have a look there, as that's probably Bionic's build environment.
In Buster, I do not see any qtbase-opensource-src package, but there is a qttools5-dev-tools package.
> What's Bionic based on - Jessie? Stretch?
Ubuntu's releases are based on snapshots of Sid.
> In Buster, I do not see any qtbase-opensource-src package,
It's a source package.
https://packages.debian.org/source/buster/qtbase-opensource-src
Same problem in Sid, same circular dependency. I wonder how they handled it? At some point, they must be importing some source package directly from QT without building it themselves? Or using scripts pointed at QT's code.
Any value in looking through the Debian qttools repository? https://salsa.debian.org/qt-kde-team/qt/qttools/tree/master/debian