Describe the bug
If you use pesde x to run a package but that has conflicting engine versions with the project in your current working directory, then it resolves the engine versions from your working directory instead of the actual package getting ran.
To Reproduce
- Initialize a new empty pesde project, and set the Lune engine to something (e.g "=0.10.2").
- Use
pesde x to run a binary package that depends on a different Lune version than you specified in the step above (e.g lune v0.8.9).
- Experience the binary package failing to run, because it runs with Lune v0.10.2 instead of Lune v0.8.9 (they treat require paths differently).
Expected behavior
The binary package should use the engine version specified in it's pesde.toml, instead of the one in your working directory.
Please complete the following information:
- pesde: 0.7.1
- Operating system: Windows 11
Additional context
Not really.
Describe the bug
If you use
pesde xto run a package but that has conflicting engine versions with the project in your current working directory, then it resolves the engine versions from your working directory instead of the actual package getting ran.To Reproduce
pesde xto run a binary package that depends on a different Lune version than you specified in the step above (e.g lune v0.8.9).Expected behavior
The binary package should use the engine version specified in it's
pesde.toml, instead of the one in your working directory.Please complete the following information:
Additional context
Not really.