Tooling management requirement 1.8. Discretionary tools specifies that we must have a way of installing discretionary tools in addition to (and in a way distinct from) project dependencies. Requirement 4.2. Persistent configuration for discretionary tools requires that we have a way of making the configuration of this installation persistent. To address this, we will design a new stanza that will specify the desired installation of tools, along with a set of rules that can effect the configured installation.
When the installation of a configured tool is effected, it the installed tool should be executable via dune exec but not available thru build rules. The design needn't account for every property we will need to configure, but it should work thru the key issues needed to allow discretionary tool installation to be developed consistent with the specified requirements.
This issue can be closed when we have a POC and design notes specifying the intended implementation design, and that design plan has been approved by some core dev.
This issues is a good place to record notes on the onging development and iterations, but those can be linked in from other sources (e.g., a document, or draft branch).
Tooling management requirement 1.8. Discretionary tools specifies that we must have a way of installing discretionary tools in addition to (and in a way distinct from) project dependencies. Requirement 4.2. Persistent configuration for discretionary tools requires that we have a way of making the configuration of this installation persistent. To address this, we will design a new stanza that will specify the desired installation of tools, along with a set of rules that can effect the configured installation.
When the installation of a configured tool is effected, it the installed tool should be executable via
dune execbut not available thru build rules. The design needn't account for every property we will need to configure, but it should work thru the key issues needed to allow discretionary tool installation to be developed consistent with the specified requirements.This issue can be closed when we have a POC and design notes specifying the intended implementation design, and that design plan has been approved by some core dev.
This issues is a good place to record notes on the onging development and iterations, but those can be linked in from other sources (e.g., a document, or draft branch).