Don't advocate use of pgk* in unified patterns. (#3032)

There are libraries with a common prefix that might introduce ambiguities now or later, e.g. zlib and zlib-ng. Prefer using `pkg/*` over `pkg*` which is more explicit. Co-authored-by: Carlos Zoido <mrgalleta@gmail.com>
conan-io · Feb 28, 2023 · d61ba28 · d61ba28
1 parent 000f2f2
commit d61ba28
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/migrating_to_2.0/commands.rst b/migrating_to_2.0/commands.rst
@@ -119,7 +119,7 @@ There are some examples:
 .. code-block:: shell
    :caption: **To:**
 
-    conan install . --build zlib*
+    conan install . --build zlib/*
     conan install . --build zlib/1.2.11
     conan install . --build zlib/1.*
 
@@ -133,7 +133,7 @@ There are some examples:
 .. code-block:: shell
    :caption: **To:**
 
-    conan install . -s zlib*:arch=x86 -o zlib*:shared=True
+    conan install . -s zlib/*:arch=x86 -o zlib/*:shared=True
     conan install . -s zlib/1.2.11@user/channel:arch=x86 -o zlib/1.2.11:shared=True
 
 Commands with have been removed

diff --git a/migrating_to_2.0/recipes.rst b/migrating_to_2.0/recipes.rst
@@ -140,7 +140,7 @@ The definition of the ``default_options`` attribute has changed when referring t
     from conan import ConanFile
 
     class Pkg(Conanfile):
-        # "pkg/*:some_option" or ""pkg/1.0:some_option" or "pkg*:some_option" would be valid
+        # "pkg/*:some_option" or ""pkg/1.0:some_option" would be valid
         default_options = {"pkg/*:some_option": "value"}