Merge pull request #4461 from conan-io/release/2.28

Sync develop2

Author: czoido

ci_tutorial/project_setup.rst

@@ -22,7 +22,7 @@ We need 3 different repositories in the same server. Make sure to have an Artifa
     $ docker run --name artifactory -d -p 8081:8081 -p 8082:8082 releases-docker.jfrog.io/jfrog/artifactory-cpp-ce:7.63.12
     # Can be stopped with "docker stop artifactory"
 
-When you launch it, you can go to http://localhost:8081/ to check it (user: "admin", password: "password").
+When you launch it, you can go to http://localhost:8082/ to check it (user: "admin", password: "password").
 If you have another available Artifactory, it can be used too if you can create new repositories there. 
 
 

reference/binary_model/dependencies.rst

@@ -53,7 +53,7 @@ This means it was using "non-embed" mode. The default of non-embed mode is ``min
 
   - If a recipe defines ``required_conan_version = ">=2.28"`` or higher, it will automatically enable the new fixed ``package_id`` computation.
     Recipes that don't update their required Conan version will still use the older ``package_id``.
-  - If the global configuration in ``global.conf`` defines the ``core.policies=["required_conan_version>=2.28"]`` it will have the same behavior,
+  - If the global configuration in ``global.conf`` defines the ``core:policies=["required_conan_version>=2.28"]`` it will have the same behavior,
     enabling this bugfix for all packages. See the :ref:`documentation for policies<reference_policies>` for more information.
   - The recommendation is to activate the new behavior via policies. It will save resources like build time, and it will also be more future-proof,
     future Conan versions might enable this behavior unconditionally.

reference/conanfile/attributes/binary_model.inc

@@ -45,14 +45,34 @@ If some package want to use both some build scripts and link with a given librar
     recommended to define it, and it should be defined in most cases.
 
 
+.. note::
+
+   The ``package_type`` attribute can also be computed dynamically in both
+   the ``config_options()`` and ``configure()`` methods, for example, a recipe might not support
+   building shared libraries in a specific platform. This can be defined as:
+
+   .. code-block:: python
+
+       package_type = "library"
+       options = {"shared": [True, False]}
+
+       def config_options(self):
+           if self.settings.os == "Windows":
+               del self.options.shared
+               self.package_type = "static-library"
+
+   where care should be taken when accessing the ``shared`` option, as it will be removed for Windows,
+   so the ``self.options.get_safe("shared")`` accessor should be used as appropiate.
+
 .. _conan_conanfile_properties_settings:
 
 settings
 --------
 
 List of strings with the first level settings (from :ref:`reference_config_files_settings_yml`) that the recipe
 needs, because:
-- They are read for building (e.g: `if self.settings.compiler == "gcc"`)
+
+- They are read for building (e.g: ``if self.settings.compiler == "gcc"``)
 - They affect the ``package_id``. If a value of the declared setting changes, the ``package_id`` has to be different.
 
 The most common is to declare:

reference/conanfile/methods/generate.rst

@@ -263,6 +263,12 @@ They can be used in the same way:
         for require, dependency in self.dependencies.build.items():
             # do something, only build deps here
 
+.. note::
+
+    By default, indexing into ``self.dependencies[...]`` returns dependencies in the *host* context.
+    If you need to access dependencies that belong to the *build* context (e.g. ``cmake``),
+    use the ``self.dependencies.build[...]`` filter helper, as shown in the example above.
+
 
 Dependencies ``cpp_info`` interface
 +++++++++++++++++++++++++++++++++++

tutorial/conan_repositories/setting_up_conan_remotes/artifactory/artifactory_ce_cpp.rst

@@ -32,7 +32,7 @@ downloading installers from `Download Page <https://conan.io/downloads.html>`_ a
 After unzipping these installers, Artifactory can be launched by double-clicking
 the ``artifactory.bat`` on Windows or ``artifactory.sh`` script in the *app/bin* subfolder, depending on the OS. 
 
-Once Artifactory has started, navigate to the default URL `http://localhost:8081` where
+Once Artifactory has started, navigate to the default URL `http://localhost:8082` where
 the Web UI should be running. The default user and password are ``admin:password``.
 
 Creating and Using a Conan Repo

tutorial/versioning/lockfiles.rst

@@ -271,7 +271,7 @@ purpose:
         "python_requires": []
     }
 
-It is relevant to note that the ``-lockfile-clean`` could remove locked versions in
+It is relevant to note that the ``--lockfile-clean`` could remove locked versions in
 given configurations. For example, if instead of the above, the ``x86_64`` architecture
 is used, the ``--lockfile-clean`` will prune the "unused" ``sound32``, because in that 
 configuration is not used. It is possible to evaluate new lockfiles for every different