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
Make sure we use esy version in package build hashes #32
Comments
More details: Here's a problem this would fix:
|
Looks like we should just completely discard the old cache when install esy? |
@yunxing Packages can form dependencies on specific versions of (I'm thinking that the global |
@jordwalke I don't know, the extra level of burrito confuses me to reason about this (you need toplevel "esy" to find nested "esy" in order to build a dependency that requires a different version of "esy"). Do you think we should prompt people to install esy globally other than making it as a dependency? (think about the case with yarn, where people have to install it globally). |
@yunxing The specific format in
Given that, suppose they have two project who are configured for two different versions of Since they have to specify which version of esy they are configured for, what if they did so by simply adding that version as a dependency. That's no more than any other way to configure.
Since it was in their dependencies, then by having the global |
Is this one done? I thought I saw this implemented. |
My latest diffs are sufficient - I include the esy version number in cache directory name. |
That will help handle esy upgrades.
The text was updated successfully, but these errors were encountered: