-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Representation for native code #270
Comments
The feature selection section in the label spec should provide a starting point for this. |
@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. |
See #269 (comment) WasmCloud already uses Bindle this way. |
Yep, see here for a full example |
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?
The text was updated successfully, but these errors were encountered: