Representation for native code

[npmccallum]

I know that bindle was designed with WASM in mind. But I thought I'd just toss out something to think about. Bindle currently has no way to represent parcel's that are equivalent binaries for different CPU ISAs. For example, what if you build the same binary for x86_64 and aarch64? How should the client know which to download?

[radu-matei]

The feature selection section in the label spec should provide a starting point for this. I think that if we specify some standard label / feature keys, this could be solved such as when requesting the bindle and a desired value for the label (in this case the architecture), the client would get the proper artifact.

[npmccallum]

@radu-matei Indeed. I had a similar thought. However, I'm worried that this will become overloaded with other concerns like build versioning (#266) and build variants (#269). All three of these concerns are vying for the same space.

[technosophos]

See https://github.com/deislabs/bindle/issues/269#issuecomment-1016671469

WasmCloud already uses Bindle this way.

[thomastaylor312]

Yep, see here for a full example