Patrick McCarty

~There was also some discussion at the time about autospec creating the package Makefile (instead of the common tooling) if it doesn't exist, so that consideration could be revisited as...

I posted a possible solution for this issue to a branch: https://github.com/phmccarty/autospec/commits/issue652 I'm not sure about this approach though, so I'll leave it there for now.

@jurobystricky I agree that test suites should not fail unconditionally in this case. One option would be to check host system capabilities prior to running the `make check` command and...

I agree that the output needs to be improved. Likely the common tooling should print the message, but it needs to compete for attention with the `for-review.txt` message... I will...

First escaping option to consider: `/usr/share/doc/libsigc++-2.0/reference/html/structsigc_1_1type__trait_3_01T__type[\[]N[\]]_4-members.html` Though a disadvantage is that the filename cannot contain spaces... double-quoting the filename combined with this form of escaping does not work.

Another escaping option to consider: `/usr/share/doc/libsigc++-2.0/reference/html/structsigc_1_1type__trait_3_01T__type?N?_4-members.html` Because the `?` is a glob metacharacter, this strategy is still not ideal, because many files may be matched. If the matched files reside...

I opted to implement option 1, simply adding `pypi-coverage` to `python-extras`. We can re-enable the coverage scans at some point after the Dockerhub image is updated to 36120 or newer.

It's out of scope at the moment.

After I implemented support for a `description` file, I still think this work is needed. It is on my TODO list.

I marked this feature request for review, since waf is not very widely used. The "projects using waf" link was last updated two years ago, so I'm not sure how...