On 2020-09-15 22:13, Kyle Edwards wrote:
Hi Drew,
Thanks for trying dh-cmake.
On 9/15/20 9:54 AM, Drew Parsons wrote:
dh-cmake has been configured to fail if debian/dh-cmake.compat does
not exist.
You can also require `dh-cmake-compat (=1)` in your `Build-Depends` as
a modern alternative. (You can even take out `dh-cmake`, since
`dh-cmake-compat` implicitly depends on this.) I don't think the
README even mentions the `dh-cmake.compat` file anymore.
I think it would work better if dh_cmake assumed version 1, unless
a different version is provided in debian/dh-cmake.compat.
I think requiring `dh-cmake-compat (=1)` is sufficiently lightweight,
but if lots of people complain I may end up doing this.
i.e. dh --with cmake should just work (as dh_make version 1), without
having to provide an explicit debian/dh-cmake.compat
Please note that the `--with` argument is also outdated, the modern
approach is to require `dh-sequence-cmake` in your `Build-Depends`.
Please let me know what you think.
Maybe it's a packaging and documentation bug?
There is no README file provided by the dh-cmake package, and no man
page for /usr/bin/dh_cmake_install
I got debian/dh-cmake.compat from reverse engineering
/usr/lib/python3/dist-packages/dhcmake/common.py against the error
message "CompatError("No compat level specified")" associated with
self._compat
My bug report is equivalent to saying self._compat should always be set
to 1, unless otherwise specified.
If the package provides the README file, then I can read it to see what
it says about setting dh-cmake-compat (=1)
