Kristoffer Carlsson
Kristoffer Carlsson
How about this: - Keep the same behavior for package projects - Do this behavior for non-package projects (like the default environment).
Just as another data point, I've still never found the current behavior desirable, and in combination with Ctrl+C not working well, it causes many fists to hit the table.
Which docs need changing specifically?
We don't assign issues to people
I should test how `instantiate` works with sub projects.
It would be nice if `dev Foo` in a subproject would just work in case it is already devved in the base project's manifest.
> it falsely displays that Automa can be upgraded: Thanks, we need to collect compat for all projects in https://github.com/JuliaLang/Pkg.jl/blob/e385b21349b6dd78aea7c81f4c2a775e96a739a9/src/Operations.jl#L2242. > When the subproject depends on BenchmarkTools but the parent...
@jakobnissen, both your issues should be solved now. There is also an update on the julia side for the corresponding PR.
Should check that `manifest = ` works when specified in the root base project.
> Which is advantage over putting stuff like relative paths in the Manifest, or fiddling with LOAD_PATH. I'll say some things that would work with this: ### No need for...