- dev a package in the global environment
- Add a new dependency to that package's Project.toml
- The global manifest's dep list for the dev'd package goes stale
- Any LOAD_PATH stacking that hits @v#.# first sees the stale deps
Isn't the whole point of dev packages that they are, well, being developed? I had expected any other environment that loads the dev package to see that the package has changed and reload its new dependencies list.
Isn't the whole point of dev packages that they are, well, being developed? I had expected any other environment that loads the dev package to see that the package has changed and reload its new dependencies list.