Brendan Abel

I don't see any reasons to vendor something that could simply be specified as a dependency that is handled at build time, so I'd prefer to get rid of them....

Do you have an example of an actual use case for this? In what scenario would a package want to use non-standard versioning to order packages as opposed to using...

Ah, I see now. We use a similar concept of "preferred versions", though we define them in curated "environment" packages. For example, we have a package called `env.maya` that artists...

Thanks for the explanation. > So instead we've switched to a runtime solve type approach, where the env is resolved when you launch the tool. This is also the way...

> Perhaps there's a misunderstanding, these are not attributes of the package. Yes, I thought this was a setting for packages. > Our 'soft' timestamp orderer is configured separately to...