René Widera

> The header checks are already only run as part of the `analysis` CI runs. All other CI runs should not run header checks. That is good to know, I...

I realized that checking out boost even with `--depth 1` took ages, we should check if it is faster to download from github the tarball.

> Or we just download the system boost in most runs, which is even faster. I also thought about it but I think it is harder to get FIBER running...

> It doesn't. It just provides one version. But I guess this is good enough for many of the CI builds. We can use an alternative boost on only a...

Removing boost should be possible for alpaka if we reimplement the compiler detection by our own. As I know this is the only part we require from boost.

> Sounds good. I don't think we need to support `add_subdirectory` anymore since we have `make install`. `make install` requires to install the library, this is one possible workflow. The...

btw: If we remove boost in alpaka we need to handle all the boost workarounds in our user code :cry:

Open parts are listed in #481. > Couldn't we do compiler detection in CMake? Or are there other parts of Boost that we are using? We can not move compiler...

I set the PR to draft to avoid accidentally merging.

> I would go the dependency way. I agree with @bussmann and would add this as a dependency instead of reimplementing it.