Jason Dillon

I just ran into this as well, but looks like you can easily solve this by defining `CONTAINER_NAME`: ``` environment_variables = [ { name: "CONTAINER_NAME" value: "replace-with-container-name" } ] ```

I don't believe use of subpath here is appropriate, as IIUC subpath is used to point to something inside of a package `subpath: extra subpath within a package, relative to...

Regarding the github org/user and repository bits, IIUC golang's module stuff doesn't require a module be a github url or a git repository (though it may mostly commonly be such)....

from https://github.com/golang/go/wiki/Modules: > Modules must be semantically versioned according to semver, usually in the form v(major).(minor).(patch), such as v0.1.0, v1.2.3, or v1.5.0-rc.1. The leading v is required. If using Git,...

Many/most component coordinate systems have a concept of namespace or group vs. name or id. So including that concept here IMO is very natural to encompass the naming schemes used...

I guess another way to look at this is that "github" and "bitbucket" are where to get something, not what the thing is. I think the github and bitbucket are...

Would it help to consider basic package-url as an identifier for what the thing is, vs. where it comes from? It may help to have a sub-spec of qualifiers that...

I am not 100% sure on the specifics, but I think that "+" needs to be URL-encoded where used. and that " " also needs to be URL-encoded. So that...

ftr my recommendation for order of qualifiers is that its non-ordered; but a recommendation for normalizing a purl to canonical is to retain input order. so if you are given:...

Okay fair enough. ---- > > Is the "qualifier strings" the entire key/value pair or just the key? > This should be the entire key/value pair. We need to clarify...