Hi there
I've had problems with activating a project because the package manager tried to install the project itself as a package somehow. Removing all the fields that didn't make a lot of sense to me to have in a project's Project.toml, i.e. name, uuid and version, and re-activating solved the issue. However, the docs say that these fields can also be present in a project. As far as I can tell, authors is the only one that can only be present in packages (I've only looked at the "top-level" fields). Just removing authors didn't cut it, though.
In general, I do find it a bit confusing that, per the documentation, there isn't any way to look at a directory with a Project.toml and being able to say whether that's supposed to be a package or a project. Running into my issue of not being able to activate my project then seemed to confirm my doubts.
Cheers,
Damian
Hi there
I've had problems with
activatinga project because the package manager tried to install the project itself as a package somehow. Removing all the fields that didn't make a lot of sense to me to have in a project'sProject.toml, i.e.name,uuidandversion, and re-activating solved the issue. However, the docs say that these fields can also be present in a project. As far as I can tell,authorsis the only one that can only be present in packages (I've only looked at the "top-level" fields). Just removingauthorsdidn't cut it, though.In general, I do find it a bit confusing that, per the documentation, there isn't any way to look at a directory with a
Project.tomland being able to say whether that's supposed to be a package or a project. Running into my issue of not being able to activate my project then seemed to confirm my doubts.Cheers,
Damian