aboutsummaryrefslogtreecommitdiff
path: root/mesonbuild/interpreter/interpreterobjects.py
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2022-02-09 16:33:34 -0500
committerEli Schwartz <eschwartz@archlinux.org>2022-02-09 16:33:34 -0500
commitab441e78b5d201c45eda415b222b0db4a543fd42 (patch)
tree792dc3fecc94b67d51f7b35d87966ac6061c4c19 /mesonbuild/interpreter/interpreterobjects.py
parentdf451f10130fc5d64cf1c65504a69bedd2fbdfdd (diff)
downloadmeson-ab441e78b5d201c45eda415b222b0db4a543fd42.zip
meson-ab441e78b5d201c45eda415b222b0db4a543fd42.tar.gz
meson-ab441e78b5d201c45eda415b222b0db4a543fd42.tar.bz2
minstall: raise explicit errors, by using MesonException
RuntimeError is way too generic when we have an explicit class for "Meson reports to the user, something went wrong". Moreover we now tell people that generic exceptions are "Meson bugs and should be reported", so our failure to do the technically correct thing and report the right kind of exception means we get haunted by demons of confusion. Specifically, people complain to us that Meson told them "there is a bug in Meson" when their install fails due to meson.build or build environment issues.
Diffstat (limited to 'mesonbuild/interpreter/interpreterobjects.py')
0 files changed, 0 insertions, 0 deletions