summaryrefslogtreecommitdiff
path: root/dev-cpp/prometheus-cpp/prometheus-cpp-1.1.0.ebuild
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz93@gmail.com>2023-05-01 00:16:57 -0400
committerSam James <sam@gentoo.org>2023-05-02 20:11:08 +0100
commit96e7f21a53c92eb4a5c4077267bb1bf1ee8accfd (patch)
tree55d139b2d22bf6d34003cd56ec4933c7b374cc3d /dev-cpp/prometheus-cpp/prometheus-cpp-1.1.0.ebuild
parenta1cd797ea1fb7d625d9fc0dc67289161c178ba15 (diff)
downloadgentoo-96e7f21a53c92eb4a5c4077267bb1bf1ee8accfd.tar.gz
gentoo-96e7f21a53c92eb4a5c4077267bb1bf1ee8accfd.tar.bz2
gentoo-96e7f21a53c92eb4a5c4077267bb1bf1ee8accfd.zip
distutils-r1.eclass: ensure meson-python uses a stable build directory
When not passing an explicit build directory, meson-python configures meson into a build directory that is rooted in a tempdir with a random suffix. This results in unstable paths, which currently disappear after meson-python completes (either with success or failure). It doesn't handle incremental or resumed builds, and it's very difficult to debug -- for example by inspecting the logfile that meson itself prints out when the configure stage fails. Bug: https://bugs.gentoo.org/905396 Signed-off-by: Eli Schwartz <eschwartz93@gmail.com> Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'dev-cpp/prometheus-cpp/prometheus-cpp-1.1.0.ebuild')
0 files changed, 0 insertions, 0 deletions