The lute development environment currently requires integrating with external toolchains for developing projects, notably a toolchain manager (e.g. foreman or rokit) for installing and executing the lute binary itself, and/or other developer tools. lute self was added as an alternative host installation mechanism for lute itself, but this installation is scoped to the users system rather than being scoped to a project-local directory, meaning that having many projects that need to use different lute versions still requires using a third-party solution for declaring and resolving those binaries.
This issue is for discussion on adding similar toolchain capabilities to lute. For ease of discussion, I will further subdivide this into two distinct "realms" of capabilities:
- Lute providing a means to manage the running version of lute itself
- Lute providing a means to manage the running versions of other tools (other than lute)
The lute development environment currently requires integrating with external toolchains for developing projects, notably a toolchain manager (e.g. foreman or rokit) for installing and executing the lute binary itself, and/or other developer tools.
lute selfwas added as an alternative host installation mechanism for lute itself, but this installation is scoped to the users system rather than being scoped to a project-local directory, meaning that having many projects that need to use different lute versions still requires using a third-party solution for declaring and resolving those binaries.This issue is for discussion on adding similar toolchain capabilities to lute. For ease of discussion, I will further subdivide this into two distinct "realms" of capabilities: