Add runtime_deploy entry (#4205)

* Add runtime_deploy entry

Signed-off-by: Uilian Ries <uilianr@jfrog.com>

* Keep symlinks detail for the section below

Signed-off-by: Uilian Ries <uilianr@jfrog.com>

* Better grammar

Co-authored-by: Carlos Zoido <mrgalleta@gmail.com>

* Avoid duplicated information

Signed-off-by: Uilian Ries <uilianr@jfrog.com>

* Keep a summary for deployers in install command

Signed-off-by: Uilian Ries <uilianr@jfrog.com>

---------

Signed-off-by: Uilian Ries <uilianr@jfrog.com>
Co-authored-by: Carlos Zoido <mrgalleta@gmail.com>

Author: uilianries

reference/commands/install.rst

@@ -124,14 +124,12 @@ like collecting licenses, generating reports, deploying binaries to the system,
 
 There are 3 built-in deployers:
 
-- ``full_deploy`` does a complete copy of the dependencies binaries in the local folder, with a minimal folder
+- :ref:`reference_extensions_deployer_full_deploy` does a complete copy of the dependencies binaries in the local folder, with a minimal folder
   structure to avoid conflicts between files and artifacts of different packages
-- ``direct_deploy`` does a copy of only the immediate direct dependencies, but does not include the transitive
+- :ref:`reference_extensions_deployer_direct_deploy` does a copy of only the immediate direct dependencies, but does not include the transitive
   dependencies.
-- ``runtime_deploy`` deploys all the shared libraries and the executables of the
-  dependencies (like ``.so``, ``.dll``, or ``.dylib`` files) into a flat directory
-  structure. The symbolic links of libraries are copied by default and they can be managed through the boolean
-  configuration ``tools.deployer:symlinks``. (Available since Conan 2.5.0)
+- :ref:`reference_extensions_deployer_runtime_deploy` deploys all the shared libraries and the executables of the
+  dependencies into a flat directory structure, preserving subdirectories as-is.
 
 Some generators might have the capability of redefining the target "package folder". That means that if some other
 generator like ``CMakeDeps`` is used that is pointing to the packages, it will be pointing to the local deployed

reference/extensions/deployers.rst

@@ -22,6 +22,12 @@ Use the ``--deployer-folder`` argument to change the base folder output path for
 Built-in deployers
 ------------------
 
+.. warning::
+
+  The built-in deployers are in **preview**.
+  See :ref:`the Conan stability<stability>` section for more information.
+
+
 .. _reference_extensions_deployer_full_deploy:
 
 full_deploy
@@ -50,18 +56,27 @@ This deployer will output your dependencies in a tree folder such as:
 
 ``[OUTPUT_FOLDER]/direct_deploy/dep``
 
-.. warning::
+.. _reference_extensions_deployer_runtime_deploy:
 
-  The built-in deployers are in **preview**.
-  See :ref:`the Conan stability<stability>` section for more information.
+runtime_deploy
+^^^^^^^^^^^^^^
+
+New since `Conan 2.5.0 <https://github.com/conan-io/conan/releases/tag/2.5.0>`__
+
+Copies all shared libraries and executables from dependencies (such as .so, .dll, or .dylib files)
+into a flattened directory structure.
+
+Since Conan 2.20.0, subdirectories are maintained and preserved as-is.
+Files are only included in environment generators when correctly specified through ``cpp_info.bindirs``
+and ``cpp_info.libdirs`` configuration.
 
 
 configuration
 ^^^^^^^^^^^^^
 
-Both the ``full_deploy`` and the ``direct_deploy`` understand when the conf ``tools.deployer:symlinks`` is set to ``False``
-to disable deployers copying symlinks. This can be convenient in systems that do not support symlinks and could fail
-if deploying packages that contain symlinks.
+The ``full_deploy``, ``direct_deploy`` and ``runtime_deploy`` understand when the conf ``tools.deployer:symlinks``
+is set to ``False`` to disable deployers copying symlinks. This can be convenient in systems that do not support
+symlinks and could fail if deploying packages that contain symlinks.
 
 
 Custom deployers