A similar thread about this issue (that also included that link):
The only question not covered there is:
Project.toml has the list of direct dependencies in the environment (those that you can load with using or import, and can also see in ]status). Installed packages also include indirect dependencies, which are listed in Manifest.toml.
All added packages and their dependencies are installed in .julia/packages, if you want to know the path to them, but you shouldn’t normally have to deal with that. You can leave the job to the Julia package manager.
wonder if some one can put a short right up connecting
depot_path
registries
environments
manifest.toml
project.toml
install vs add packages
what should one care and what is internal
overview of quick installation directory of Julia or JuliaPro
Nevertheless, what you cite is the default value (which may change in some configurations). The best way to know where DEPOT_PATH points at is just looking its values in a Julia session:
A short answer to your last question is that you can modify the DEPOT_PATH with environment variables - see the links in the manual and the reference above.
But since you were also asking for tips “for starters”, I’d say that modifying DEPOT_PATH is not the most recommendable exercise for starters. Normally everything should work fine leaving it as it is.
I think that this applies specially if you are using Julia Pro: that’s a distribution of Julia that I think is specially useful for that type of users who don’t want to do any kind of hacking to have an IDE, or deal with broken packages, etc. That kind of user I’m thinking on, doesn’t want to touch the package depot either. (Well, another type of Julia Pro users would be those working in some context that makes worthwhile to pay for Julia Computing’s support, but in that case you could ask them directly.)
Its recommended not to edit this file in your JuliaPro installation, please use (Create) following file if you need to add any functionality in your JuliaPro startup
I am not intending to change anything. I just want to understand. Packages and how they behave (as they are the basic libraries) for I think that is 101.
Looks like the tentacles are a bit deep and is in many places.
I thought a pre-configured install like JuliaPro would help.
You can search for packages using juliahub. I dont know of a method to search for packages you have installed locally like that, unfortunately. Perhaps Pkg.installed()?
If you want to understand, I think the best place to learn is the documentation pages of the package manager: 1. Introduction · Pkg.jl
But I’m afraid that this is not material “for starters”. For them, I’d rather recommend the more basic summary in the Julia manual: Pkg · The Julia Language