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
The repository now includes a Project.toml (supported with the version range of dependencies) and a Manifest.toml (specific version of the complete dependency tree). Given the discussion here and here I am wondering if we should not remove the Manifest.toml to reduce the potential of versioning conflicts.
The text was updated successfully, but these errors were encountered:
The links you provide suggest not to include Manifest.toml.
These files are generated by Julia, as is indicated by their first lines. Generally, my git policy is to avoid including such files in any sort of project, Julia or not. By analogy, in a C/C++ based project, we would not include .o files, which are generated by the compiler. A problem with including such things in a repo is that the developers might start receiving some ill-thought-out pull requests, as novice users might think that changes ought to be transmitted back upstream.
It's pretty easy to add it back to the repo, if problems arise.
The repository now includes a Project.toml (supported with the version range of dependencies) and a Manifest.toml (specific version of the complete dependency tree). Given the discussion here and here I am wondering if we should not remove the Manifest.toml to reduce the potential of versioning conflicts.
The text was updated successfully, but these errors were encountered: