I am currently assembling a pull request for the Octave packages list at gnu-octave.github.io.
I am pretty confident that my package can be installed fine, once the target system has the requirements fulfilled (some build tools, dependent C++ libraries), since it works on several machines CI pipelines install it regularly on a Gitlab instance. These requirements are not fulfilled of course in the environment which is used by the Github check job, see for example New package: caosdb by quazgar · Pull Request #10 · gnu-octave/packages · GitHub.
What is the expected behavior of some package’s configure script in such cases? Should I rewrite it to exit gracefully, maybe outputting a message for the users with a reference to the package’s documentation? Or is it OK to fail?
In case this is relevant, the package
yaml is at Octave-packages/caosdb.yaml at new-package-caosdb · CaosDB/Octave-packages · GitHub, the package caosdb itself can be found at CaosDB / CaosDB Octave library · GitLab
Any hint would be appreciated