You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever I create a new project, I will forget to activate the new project's directory as an environment for installing packages. So I always install the packages into the default @#.# and later realize that no Project.toml was created. Then I uninstall the packages from the default environment and create the new Project.toml.
Thus, I would like to request a feature which can lock an environment, for example the default one, so that I get an error message if I try to install packages.
The hack I am currently using already implies a possible implementation: I did chmod a-w ~/.julia/environments/v1.10, which leads to an error when I try to add a package:
Whenever I create a new project, I will forget to activate the new project's directory as an environment for installing packages. So I always install the packages into the default
@#.#
and later realize that noProject.toml
was created. Then I uninstall the packages from the default environment and create the newProject.toml
.Thus, I would like to request a feature which can
lock
an environment, for example the default one, so that I get an error message if I try to install packages.The hack I am currently using already implies a possible implementation: I did
chmod a-w ~/.julia/environments/v1.10
, which leads to an error when I try to add a package:Broken down into individual tasks, the implementation would be:
Project.toml
is read-only, show a concise error message explaining that the environment is 'locked'.] lock
and] unlock
to set the permissions ofProject.toml
andManifest.toml
to read-only and rw accordingly.The text was updated successfully, but these errors were encountered: