Nathaniel McCallum

FYI @tarcieri

Specifically, this problem arises when upstreams already use the `build` field of semver. For example, https://crates.io/crates/rdkafka-sys whose current upstream version is `4.2.0+1.8.2`.

@radu-matei I'm not sure I'm actually making an ask here. If I were to rephrase this issue, the problem is that while semver allows for build metadata, this metadata is...

We're basically at the crossroads of the Enarx project trying to decide whether to invest a person on Bindle or to build our own. I'd really prefer the former since...

@itowlson That is an internal implementation detail. The API would need to reproduce the invoice byte-for-byte as it was uploaded. But you can store the semantic meaning any way you...

Let me try to rephrase the problem another way. Let's say that a Bindle server gets compromised. During the compromised period, workloads were deployed from Bindle. The Bindle server and...

One could just say that bindle's scheme represents the build variant and version and be done. However, the reality is that consumers of these build artifacts almost always want to...

I understand the need for a canonical invoice. What I don't understand is Bindle wants to have non-canonical invoices. Clients will need to grok the canonical invoice in order to...

@fibonacci1729 What use case requires semantic identity?

> I think we discussed the semantic identity thing at length on a call a while back, but here's the summary: > > * We want the server to be...