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
which should leave the Project.toml (packages/Foo/Project.toml) and Manifest.toml (../../Manifest.toml) without any changes
But we see
(Foo) pkg> add Example
Resolving package versions...
Updating `~/packages/Foo/Project.toml`
[7876af07] + Example v0.5.3
Updating `~/Manifest.toml`
[7876af07] + Example v0.5.3
(Foo) pkg> rm Example
Updating `~/packages/Foo/Project.toml`
[7876af07] - Example v0.5.3
No Changes to `~/Manifest.toml`
This is a bit of an inherent drawback with the current manifest = system that exist in Pkg in that it doesn't take into account any other projects that have a manifest = entry that points to the same manifest. In order to be "safe" it therefore never removes any packages from the manifest since it could be so that other projects are using it. A full "sub project" implementation would consider that.
This is an issue for packages setting the
manifest = ...
argument in theirProject.toml
The problem we're seeing is that, if you have a package
Foo
with aProject.toml
(at e.g.packages/Foo/Project.toml
) which looks like:note the
manifest = "../../Manifest.toml"
entryAnd then you add and then remove a package
which should leave the
Project.toml
(packages/Foo/Project.toml
) andManifest.toml
(../../Manifest.toml
) without any changesBut we see
And the
Manifest.toml
is left with a diff like:Which has the issue:
The(fixed by Update manifest entry of project for non-local manifests #3579)deps.Foo
entry is left withExample
in itsdeps
deps.Example
entry, even though nothing depends onExample
(given thatFoo
doesn't depend onExample
after therm
)The text was updated successfully, but these errors were encountered: