One of the reasons to introduce Pkg3 and the code loading rules was to make projects more reproducible.
This is why the following behaviour surprised me: when I switch to a new environment (
] activate myenv), it is added to the environment stack (which now looks like
[myenv, v1.0, stdlib]). This makes it difficult to make sure that I am not relying on packages that are part of the default environment, but not
myenv and thus that submitting the manifest for
myenv provides a full working environment to the end user.
Is there a way to replace the default environment instead of adding to the env-stack?