From ca4ccc03ffdf65c965ec070601ef95344eecd228 Mon Sep 17 00:00:00 2001 From: Steve Kelly Date: Fri, 10 Nov 2023 14:12:56 -0500 Subject: [PATCH] docs: add `manifest` field documentation to Project.toml guide in Pkg.jl manual This should be mentioned here. Added in: https://github.com/JuliaLang/Pkg.jl/pull/3579 --- docs/src/toml-files.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/src/toml-files.md b/docs/src/toml-files.md index 4bf84568b0..6ee05f3be4 100644 --- a/docs/src/toml-files.md +++ b/docs/src/toml-files.md @@ -77,6 +77,17 @@ Note that Pkg.jl deviates from the SemVer specification when it comes to version the section on [pre-1.0 behavior](@ref compat-pre-1.0) for more details. +### The `manifest` field + +`manifest` specifies an external manifest file (`Manifest.toml`) for the project. This is particularly useful for managing package dependencies in a more granular or shared manner across multiple projects, for example: +```toml +manifest = "../Manifest.toml" +``` + +This specified `Manifest.toml` does not need to be a subset of the project's own manifest. +The project inherits any version constraints or package specifications from the referenced manifest and is integrated into the dependency resolution process. + + ### The `[deps]` section All dependencies of the package/project are listed in the `[deps]` section. Each dependency