Adrien Destugues

You can configure debug_server to silently kill the crashing program: https://www.haiku-os.org/docs/userguide/en/applications/debugger.html Not sure if that can be done from inside a recipe, however.

Yes, the latest version with my fixes is on haikuarchives. Jua made his version private so I based my work off Diver's backup copy.

It would be a lot simpler to make the recipe build directly from https://github.com/owenca/llvm-project/tree/haiku-format which is a version of clang and llvm already patched with haiku-format patches. That is how...

For me it's easier to work with the full repository at least in the context of haikuports packaging. I will let owenca say if he has any preference.

> Whatever a "GHA" is... I guess it is short for GitHub Actions, where they run their testsuite using Github infrastructure automatically for each commit.

The manual population of these variables is also a sanity check. It allows to make sure nothing disappeared from a recipe without anyone noticing (because of a picky configure script...

These files are used by the Haskell package manager to keep track of what's installed. They need to be writable by the tool (cabal). There may be a more appropriate...

All packages depend on the Haiku package, and the Haiku package includes the licence already (in /system/data/licenses/). Isn't that enough?

The COPYRIGHT variable should indeed be kept closer to the original. However, nothing in the MIT licence mentions that the copyright notice and the permission are to be kept together...

This sounds quite annoying for licences that are already used in Haiku itself. I would not add any symlinks: it does not solve the issue (the package still does not...