Alexander Huszagh

Since all the OpenBSD targets are tier 3, and they seem to have only stayed at GCC 4.2.1 (pre-C++11, I have no idea if they supported later), and binutils ld...

Does this still need to be a draft? Should be good to go, and since this is opt-in, we don't have to worry about breaking changes or anything.

Now that we've merged breaking changes for v0.3.0, this is ready for merging once all the conflicts have been fixed.

We could test for a single platform on macOS and Windows, build a single image fetched from cache (choose one unlikely to change for the best performance) and just install...

> That should work, there is one thing to be careful of then however, changes that break mac/windows won't be catched if the conditions needed to break are not in...

The idea behind this is so we can provide native toolchains if the image platform and the cross-compilation target are the same. This simplifies our logic for say, `linux/arm64` images...

> I'm not sure I understand what this does and how it differs. How is it used? Say if I want to build `aarch64-unknown-linux-gnu` for an image running Ubuntu:20.04 on...

> with buildkit it's possible to do conditional stages, I think that could help to not use a script file > > ``` > # arm64-specific stage > FROM base...

bors try --target x86_64-unknown-linux-gnu

Based on comments elsewhere, I should clarify that this is not used to publish a `ghcr.io/cross-rs/native:$tag` image: it is meant so `Dockerfile.native` is used for `ghcr.io/cross-rs/x86_64-unknown-linux-gnu:$tag` on `linux/amd64` and `ghcr.io/cross-rs/aarch64-unknown-linux-gnu:$tag`...