Closed topolarity closed 2 months ago
The reason for this is that when Pkg reads a project and sees that it is both a weakdep and a dep it ignores the dep entry (so that extensions can be used in a backwards compatible manner).
The solution here might be to just delete the weak dep entry when an explicit add
is made.
But on the other hand, having extensions while having strong deps on the triggers for those extensions is very likely to run into a cycle analogous to https://github.com/JuliaLang/julia/issues/52511#issuecomment-1983388150.
If you
pkg> add
a package that's already in your Project.toml as a weakdep, Pkg gets mildly indecisive and installs all of the package + deps only to remove them on the next package operation.MWE:
It is a bit concerning that
> add Foo
can have an inconsistent concept of the state after an add versus the rest of Pkg.