nickajacks1

Hermit is probably not taking every specified package into account when running `hermit install`. There is a second manifestation of this issue: given packages `testbin1` with versions `1.0.0` and `1.0.1`...

I believe q value negotiation is [already implmented](https://github.com/gofiber/fiber/blob/main/helpers.go#L404). Might want to check the accuracy of the rest of the findings.

There is a way to parse media type params with the standard lib ( https://pkg.go.dev/mime#ParseMediaType ) but I didn't use it because there was a desire to minimize impact to...

It seems like the real problem in this issue is that the cache lock is non-reentrant, meaning you cannot use hermit-installed binaries in a package trigger if they are not...

@alecthomas this was fixed by #436 @lnanctx upon the next hermit~ release, you can do this: ```hcl # ~/.hermit.hcl defaults { sources = ["https://github.com/cashapp/hermit-packages.git", "https://github.com/lnanctx/home-packages] } ```

With a package that uses "${version}" but has a channel that does not set version... ```hcl source = "example.com/${version}" channel "foo" {} ``` ...Hermit currently errors out with an error...

Updated to simply give a more helpful error message.

force push to fix gofmt

Rebased, haven't changed approach yet. Still thinking. This is the first time I've really missed `const` in go :)

I think I'm going to close this in favor of pursuing two lower-impact changes: * Change the PackagePredictor to avoid the Search function in favor of a faster glob-like search...